So I've been using heroku meme api on my discord js bot, it was working fine untill today when it didn't respond I decided to check the website but when I opened it it gave me an application error, idk how to fix it any help would be appreciated the link I use is
https://meme-api.herokuapp.com/gimme
Heroku has discontinued free dynos and data services, it's possible that API was using those.
https://blog.heroku.com/next-chapter
I have made a simple bot for Google Chat, which has been working perfectly fine for the past couple of weeks. I tried to make a change to the API configuration for Hangouts Chat, and am greeted by this error.
I have tried making different changes to the API, and receive the error every time. Even simple things such as disabling the bot status gives me the same issue.
I tried re-making the project from scratch, as well as trying a different account on the same domain. The issue persists.
My situation: I wanted to change my app name on heroku. I have done so with Heroku CLI and get confirmation that change was success. However, after this change I've started to receive a weird errors on mLab.
From my panel I can see that there is no user to connect to DB, but when I create one, it is deleted after relogin and get same error. Did anybaody face such a problem? Did you manage to find a solution?
I've checked status page and there were no issues. What's more I tried to contact support, but without any response (it's only sandbox, so I't quite obvious that my question will be replied last.....)
Contacting support helped. But I have got no info what was wrong.
I'm currently visiting Egypt and skype stopped working after a few days. It gives me "Skype home unavailable" and the status icon keeps spinning. I already searched the net for this issue and tried a few things which did not work. I also tried web skype and it the status icon shows green but messages don't go through anyway. I'm not asking about this general issue which seems to have many possible sources.
Now, while searching for this problem I came to realise that some web pages from skype web site are also not accessible, and I suspect it is either a HTTPS protocol configuration, or the Internet service is blocking skype.
For instance, this page:
https://support.skype.com/en/faq/FA10953/how-can-i-update-my-windows-firewall-settings-after-reinstalling-or-upgrading-skype
does not work in Firefox ("Secure Conection Failed") and in IE11 it only started working after after I actived SSL 2.0 and 3.0. Still, although skype-web opened once now I'm not even able to open it.
The address https://web.skype.com/ retuns "This page can’t be displayed" in IE11. And the button "Fix connection problems" finds nothing. After a few retries it seems to work out. Skype messages eventually eventually seem to get through but I can never do a live chat or a call or even a real phone call.
So, any idea why I can't access this and other skype pages? Is there some updated authentication protocol not well supported? Is there a way I can track it (I'm not a network specialist but maybe I can try something).
I found about blockage in Egypt: http://stepfeed.com/more-categories/big-news/egypt-blocks-popular-voip-apps-monitoring-facebook-skype/#.V0M9uVIiggQ
but I was able to use it when I arrived.
I started using Microsoft Bot Framework and followed step by step all tutorials.
I has been able to register a new bot and to deploy it working good with emulator, but except it nothing else works.
Test connection to your bot chat do not works despite I get answer from emulator and from all connected channels, that where created and registered properly I always get an Unauthorized response or something like that, anyway no response, so nothing works.
I tried with Twilio, Web Chat, Telegram (Skype auth is pending) getting always the same response.
As it seems I strictly followed the tutorials, is there something else to do or to be approved? Or just the service is still not working at 100% as too young?
Thanks
If you are using HTTP you need to disable basic auth because the connector won't send your appSecret in the clear.
The solution is to make sure you register as HTTPS, or if you need to use HTTP then disable the basic auth.
Took me a while to get it working locally too. Oddly for me it only works when those 'secret' fields are empty, as mentioned and running in debug.
Running without debugging seems to always result in a 401
Hi I was facing same problem to work bot locally in v3. I just made everything blank in web.config and it is working.
I solved the problem.
It was related to https. It's not well explained into tutorial but when you create and publish a service in Azure it is created as http://XXXXXXX.azurewebsites.net as shocased into tutorial, but it will not work as your service must run in https.
I so used https://startssl.com to create a free ssl certificate then turned on SSL into my Azure service so everything started working.
I've cleaned up the getting started with the following; hopefully it will make it clearer for the next person who uses it:
Click the “Register a Bot” button and fill out the form. Many of the fields on this form can be changed later. Use a the endpoint generated from your Azure deployment, and don’t forget that when using the Bot Application template you’ll need to extend the URL you pasted in with the path to the endpoint at /API/Messages. You should also prefix your URL with HTTPS instead of HTTP; Azure will take care of providing HTTPS support on your bot. Save your changes by hitting “Create” at the bottom of the form.
Make sure you are using HTTPS. BotFramework will not work with basic auth so tokens are not passed in the clear.
See: http://docs.botframework.com/connector/calling-api/
Make sure that you republish your bot service after registering and getting the app Id and password. If you fail to do this you will get Unauthorized. The steps are 100% clear on this and I hit this for a minute.