This is the issue I am getting:
application-169dad56b7bb7d53e3aaeaf87e8fc05c.js:156 Pusher : Error : {"type":"WebSocketError","error":{"type":"PusherError","data":{"code":4001,"message":"App key 2395af13c928012b447b not in this cluster. Did you forget to specify the cluster?"}}}
This error means that you haven't specified the Pusher cluster to connect to, or specified one that is not the same as the one your app was configured to use in Pusher's Dashboard.
Specify the cluster to connect to as described here. The cluster your app is configured to use is shown at the bottom left of your app's page in the dashboard.
Related
I'm trying to configured an Azure Application Gateway in front of a web app. The web app is empty for now, only a single page to verify its running. I've added a custom domain and dns settings, verified in the network settings of the webapp. I've setup the AG following a few different links as I couldn't get a working example from a single source. I'm at the point now where my health checks are returning a 301. The lister is using port 80 as I have not setup the ssl yet. The app custom domain has no ssl binding either. The network security group has the default settings. I've checked the webapp before adding the private ip and it was fine, its just an empty page. So i'm wondering what could be causing the 301. Anyone have an idea what could be causing that or some further links I can check?
Thanks.
Resolved. The webApp had Https Only turned on in the settings, that was the cause of the 301. Doh!
I am trying to configure JDBC but kept getting the same error I am getting using snowsql:
250001 (08001): Failed to connect to DB. Verify the account name is correct: JG3409.canada-central.azure.snowflakecomputing.com:443. 000403: 403: HTTP 403: Forbidden
If the error message is unclear, enable logging using -o log_level=DEBUG and see the log to find out the cause. Contact support for further help.
Goodbye!
I have configured the config file, and I have double checked the account, company, region, reset password to only use alphanumeric.
I have used both forms of the URL
The only possibility is that I am using a trial account, but I can't imagine that this would limit external non-browser connections?
I use a simple user/password, I have whitelisted my IP and I don't have a problem with a proxy or a firewall. I can successfully connect using a browser.. using:
https://app.snowflake.com/canada-central.azure/jg63409
Important contents of the config file:
[connections]
accountname=JG3409
#accountname=uegxydq-pz20606
region=canada-central.azure
username=ASHSNOWFLAKE
any ideas?
Your account is not JG3409 but JG63409 based on this link:
https://app.snowflake.com/canada-central.azure/jg63409
Try in your browser:
https://jg63409.canada-central.azure.snowflakecomputing.com
I found out using snowcd that my computer could not connect via my home router.
When I used my personal hotspot on my (5G) phone, snowcd passed all the tests immediately. The problem then arose how to adjust the network security policy to allow a CIDR block of network addresses through since my phone uses a new address every time I connect, and I can't edit the policy to allow my phone while connected via my phone (for obvious reasons)
Catch 22
123.45.0.0/16 is not accepted in the new Snowflake UI, and 0.0.0.0 doesn't work for me, but the documentation gave me a clue.. the new UI doesn't separate by commas, so I switched to the old UI and voila!
Incidentally the OLD UI uses the same URL as SnowSQL so I picked up my error in my account number there as well (although I should have seen it earlier).
Diabolical but thanks #Sergiu too!
We have exposed a url to Twilio to send the sms delivery status and it was working fine when we hosted our service in our own data center.
But we moved our services to aws ; Twilio is unable to call our service and it showing the below error
https://www.twilio.com/docs/api/errors/11200
please help
make sure your Elastic IP Address is reachable using TCP/443 (you enabled this on your EC2 instance, correct) and your application supports both GET and POST methods. Check the Debugger (small bug icon in upper right corner of console) for any relevant error messages, otherwise the error 11200 URL you provided has a lot of extra steps to check.
You should be able to reach your application via your web browser, for testing.
Which IP addresses will Twilio's requests come from?
I followed the instructions to create a transparent gateway and successfully have a leaf device send telemetry to the IoT Hub via the gateway. However, I noticed that as soon as I set the certificate on the gateway, all modules installed (except for the Agent and the edgeHub) on the Gateway stopped functioning (even with the sample tempSensor). The Azure portal even showed that my edge gateway is disconnected (the telemetry still got through). I tried the log on the tempSensor module and it shows that there are some issues with the certificate (shown here)
Do you have any idea how to solve the problem? It is kind of pointless to gateway without any module on it.
Also, I want to pre-process the received messages from the leaf devices before sending to the IoT Hub. I know how to route the messages between modules (as in the tutorials) but how to route the messages from the leaf devices to a module?
I have no immediate idea about the certificate issue but in regards to the routing from leaf devices to a module this config should work:
"leafToFiltermodule": "FROM /messages/* WHERE NOT IS_DEFINED($connectionModuleId) INTO BrokeredEndpoint(\"/modules/filtermodule/inputs/input1\")"
The clue is WHERE NOT IS_DEFINED($connectionModuleId) which filters out all messages which are sent by other modules on the Edge device itself and only routes messages from the leafs
We are facing a strange problem with APNS.
We have a live app and it is able to send Push Message from the API domain. But we are preparing to move it to another server where we are testing with the IP instead of domain.
We are using the same settings and code, but APNS keeps failing returning the following error:
NOTICE: Failed to connect to APNS: 0 .
We have checked thoroughly, we have 2195 and 2196 ports open and SSL installed on our new server.
Can anyone please tell me if APNS keeps failing because of using IP instead of domain name?
Regards,
SG
Apple docs say:
The IP address range for the push service is subject to change; the
expectation is that providers will connect by hostname rather than IP
address. The push service uses a load balancing scheme that yields a
different IP address for the same hostname. However, the entire
17.0.0.0/8 address block is assigned to Apple, so you can specify that range in your firewall rules.