My application shuts down sometime with the following error in the console:
PlatformApplicationDisabledException
I've reached out to aws service team to investigate what I was doing wrong in my program.
So, they have replied that:
PlatformApplicationDisabledException is triggered when the downstream
push-notification service rejects the credentials provided with the
request.
In your case, the downstream provider is APNS_SANDBOX. Ensure that you
are using valid Sandbox credentials with your APNS SNS application.
Apple rejected your credentials, likely due to them being expired, or
for a production application.
Can someone guide me to resolve this issue.
Thank you.
Related
I have developed a bot on node.js as a teams app using the yo teams generator. The bot is hosted and deployed on an azure app service web app. The bot was working fine all the while, but started throwing http 500 internal server errors in the past couple of weeks.
I am not sure what has changed, but I am trying to fix this issue but not finding any leads and useful information from appInsights or the trace logs. All I see is the below exception being thrown in appInsights:
"POST to the bot's endpoint failed with HTTP status 500"
The bot works perfectly fine locally, when debugging through ngrok. Please let me know how I can fix this or where I can look for useful logs to help resolve this.
I was able to resolve this with MS on a support ticket. Looks like the fix is to update the configuration setting to reflect the latest version of node from 12.13 to 16.13.0 in the app service config section.
I am getting okta login page and when it authenticates, i am calling token endpoint to get the tokens it works super fine from my system. But when I deploy it in integration system, its throwing me java.net.ConnectException: Connection timed out (Connection timed out) error. I am assuming it could be because of firewall issue.
Is my assumption is right? If yes, What kind of details i have to provide to open firewall?
Do I need add/check something else?
Below is from my okta server log. After I am getting exception.
Please help.
Just go to your deployment environment and try to curl to your authZ server /token endpoint with a GET request. You will immediately see if there is an issue with the connection. It may be as simple as providing a proxy for the connection, or something else. Your network team should help you, when you tell them Okta endpoint, you are trying to reach
I've created an Watson Assistant and pasted the OpenWhisk Action Endpoint URL to my Alexa Skill as described in this GitHub Repo.
Everything worked fine so far. I was able to send questions to my Chatbot by talking to the Alexa Simulator and received the expected answer which was read out by Alexa. But if I launch my Alexa skill now I get the response "I am unable to reach the requested skill". The Endpoint URL is correct as well as the SSL Certificate Type Configuration in the Alexa Simulator. I did not change anything but suddenly it does not work but used to work fine before. Any ideas?
I tried to send the Launch Request as Manual JSON from the Alexa Simulator and received "Cannot establish SSL connection to your skill endpoint" as output JSON.
Furthermore I found the following from the Alexa Simulator logs:
"The SSL handshake to endpoint Resource [https://eugb.functions.appdomain.cloud/api/v1/web/hhzStud_AIA_projekt/default/watson-alexa-hhz-skill.json], Type [HTTP], Region [DEFAULT] failed. Please check that your java keystore is correctly configured"
I checked my acttion using the following command ibmcloud fn activation list and got an application error (IBM Docs Link)
Why can't Alexa reach my Endpoint? It used to work before without any problems.
Thanks
It appears to be an issue between Alexa and the endpoint deployed on IBM Cloud. Make sure to use https://eu-gb.functions.appdomain.cloud and not https://eugb.functions.appdomain.cloud as listed in the description.
I can access https://eu-gb.functions.appdomain.cloud/api/v1/web/hhzStud_AIA_projekt/default/watson-alexa-hhz-skill.json and it uses a Let's Encrypt certificate with below details:
A similar issue was reported in https://forums.developer.amazon.com/questions/106526/getting-ssl-handshake-failed-error.html and a response pointed towards this list of requirements for your web service https://developer.amazon.com/en-US/docs/alexa/custom-skills/host-a-custom-skill-as-a-web-service.html#requirements-for-your-web-service.
Maybe it helps as a starting point to verify what is missing.
I loaded the EchoBot template from Microsoft here: https://marketplace.visualstudio.com/items?itemName=BotBuilder.botbuilderv4
I started a new project and try to run it locally. No MicrosoftAppID or MicrosoftAppPassword is provided.
Then I loaded the latest Bot Framework Emulator v4.7
I connect locally, again no App ID or App Password:
However when I try to send a message I get unauthorized error, why would I get unauthorized error when connecting locally?
The server is definitely running locally and the local URL is correct:
One question I want to ask is the login dependent on any 3rd party URL call? My company security policy is blocking all URL unless whitelisted, so if this is the case, maybe the authentication is blocked? What would be the URL for me to whitelist?
EDIT: I tried it a VM outside of the company network and it works! So something must be getting blocked. Any idea?
I got around it by using a VM outside the company network instead. It's not a solution, but it is a work around. I highly suspect some port are being blocked by company firewall but not sure what so I am not sure how to get it whitelisted.
I am using Amazon SNS service to send push notification.
But today, it suddenly stopped working.
I can't create another Application endpoint, it says -
APNS Sandbox certificate is invalid
and I can't update credentials, the error is -
Request could not be completed (Service: AmazonSNS; Status Code: 500; Error Code: InternalError)
I am able to send push notification using the same p12 file with another software i.e. https://github.com/noodlewerk/NWPusher
What could be the problem?
How can I troubleshoot this issue?
Please help.
Thank you!
The reason for the problem was that (this is my guess) - I sent push notification with incorrect format.
That must have returned error code and because of that the connection between Amazon SNS to Apple server was closed. (It should be kept open always)
Because Apple thinks this as some kind of an attack.
The only remedy is wait for few hours and try again.
This is mentioned in the Technical Note here - https://developer.apple.com/library/ios/technotes/tn2265/_index.html
Even i had the same issue yesterday, it started working few hours back. can you confirm?
I spent whole day generating and testing certificates without any luck, and its working now with the same certificate.