Smoochbot not replying - heroku

I tried setting up smooch-bot via the Heroku example. I followed the directions and opened the heroku app and chatted with the bot, but I don't receive any replies. The messages I type are being forwarded to smooch because I am receiving email notifications from Smooch... but there are no replies from smooch-bot in the chat window.
I am not a programmer so I've tried to follow the directions. I am deploying the app via a Dropbox connection. Is it normal that the Heroku folder in my Dropbox is empty? I tried uploading script.js into Dropbox > Apps > Heroku and Dropbox > Apps > Heroku > mybot, but I'm still not getting replies.
I am not sure where I went wrong. Could somebody help me point in the right direction?

If you're using Dropbox with Heroku, its not enough to simply edit your script file. You have to explicitly deploy your Dropbox changes via the Heroku dashboard, like this:
Also, to debug any issues with your bot script specifically, I've documented some troubleshooting steps here:
https://github.com/smooch/smooch-bot-example#troubleshooting-your-bot
To summarize, you need to install the heroku toolbelt, log in on the command line and view your app's error logs with heroku logs -a your-app.

Related

Heroku meme api gives me application error

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

Heroku says my custom domain is already in use, despite having already released it

When I attempt to add a new custom domain to my heroku app, I receive the following error
Domain "..." could not be created:
... is currently in use by another app.
See this image:
Example of error in the add new domain sidebar
Details so far:
I use a free dyno for my app
I own the domain and do not use it in any other heroku app (in fact, it's unused for any website)
I used this form, Heroku Domain Release, to release the domain from any existing usage on Heroku. This was successful and seems to imply it was in use by another app at some point.
I ran that form again, and received the message that it was no longer in use by any app.
It's been at least an hour since I tried using the release form and I still receive the same error message when trying to add my domain.
I cannot contact Heroku support directly since I use a free dyno.
Any help greatly appreciated!

Is the a way to get the logs from Mailgun to understand why it's not submitting on my Heroku website?

I'am working on AWS Cloud9 developing a website. I have transferred my Ruby on Rails App from Cloud9 to Heroku servers. I received a Heroku domain and choose to add on the Mailgun Service. I have signed up to Mailgun and I've tried to test the service. Everytime I click the submit button on my website, I receive the message, "We're sorry, but something went wrong.
If you are the application owner check the logs for more information."
This is problem starting on the Heroku side? or the Mailgun side? I've used the recommended ports.

Failed to send activity: bot returned an error 502 404

I'm trying to deploy the ms teams auth bot to azure. The bot gives a welcome message when I tested it using the bot framework emulator. Then I ran these steps to deploy my bot to azure. During the deployment steps, I used the same app id and password throughout the whole process. Then I tested it on azure and it just fails:
I look at my browser's network requests and I see this:
HTTP POST: https://webchat.botframework.com/v3/directline/conversations/JYtg14OvcjS7FiNwCMXzH1-g/activities
Response:
{
"error": {
"code": "BotError",
"message": "Failed to send activity: bot returned an error"
},
"httpStatusCode": 404
}
I streamed my application logs and it gave me a big HTML response you can see here. But it's just a 404 page response.
I tried to run this in my bot emulator, pointing to the bot in production and it gave a 404 response as well:
Edit:
I just tried to redeploy my bot but got the same results when testing my bot.
After running all the deployment steps, I never had a web.config file. Though testing it in my bot emulator locally works fine.
Here is a screenshot of my resource group, which has 3 resources:
Here is a screenshot after running the pre-deploy command. It doesn't generate a web.config file, but it generates a .deployment file:
The app ID is the same in app registrations portal in azure, and the same in my appsettings.json file, and the same when I ran the deployment command.
Edit 2:
Here is how I zipped my project:
On Azure, I'm not able to view my code while I remember that I used to do it before. Perhaps it's because on Azure, I only have a Bot Channels Registration but I don't have a Web App Bot. Is that a problem?
Edit 3:
I noticed I did not include the .deployment file when I zipped the contents. (The file explorer was hiding the file.) So now I included it in my zipped contents and redeployed by bot again. (Unfortunately, the bot is still behaving the same.)
Here are the new contents of /dev/wwwroot/:
Here is my app registration (I tried toggling both account types instead of re-recreating it through command line, still same bot behavior):
The .deployment file was zipped. My mac just didn't show it. I updated the screenshot to show my .deployment file above.
OPs issue ended up being that they need to make their App Registration available for ALL accounts, including personal. To do so, follow these steps
I'll keep the answer for posterity, but if you're running into this issue, my comments provide good troubleshooting steps.
Aha! The issue was this step. You need to zip up the contents of the project folder and not the folder itself.
This:
Instead of this:
When you deploy, your folder structure will look like this:
You aren't the first person to run into this. I've created a PR to clarify this. Let me know if you think the change I made should say something else.
Sidenote: The web.config is created upon deployment. My mistake with that comment.

Heroku app name change and mLab mongodDB timout

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.

Resources