I'm trying to deploy my NestJS app on Heroku but now all of the sudden app is throwing Bad Auth error.
On the development it's all working fine.
This is the error I'm getting:
I'm storing the credentials in .env
Are these constants populated by Heroku with some unexpected values?
And I'm allowing the connection from every IP address:
What is going on and how to fix this?
I was having the same trouble, the solution for me was to put the whole link to connect in an environment variable instead of just the secret. I was using node, express, mongoose and MongoDB Atlas, so for me it was:
//on .env file
ATLAS_CONNECT=mongodb+srv://yourusername:yoursecret#cluster0.mre5gvd.mongodb.net/yourDBname
//to connect
mongoose.connect(process.env.ATLAS_CONNECT);
Related
I have a database credential that I worked with on development. Starting the server gets me the response message as expected. A GET request route fetches data from a MySQL database that I configured. All these work perfectly on local env. When I deployed to Heroku, I used the same db config credentials exactly how I used them on dev env. But here, I get the default response message on home route, but when I route to get data from the database I get this {"message":"connect ETIMEDOUT"}. What could be wrong?
I am trying to use heroku connect with my salesforce instance.
I have added Heroku connect as addon together with my postgresql.
This is what I am getting when I am clicking on it:
Am I missing some misconfiguration? What can I check?
This was due to a conflicting behaviour between two heroku users connecting.
on the cli I have one user meanwhile in the browser there was another user connected
I have been using Heroku Redis to power Django Channels for a while. My old, existing implementation works. I tried to set up a new app in the pipeline, but when I provision a new Heroku Redis resource it generates it without a username. When I try to use that URI to connect Channels it gives me a 104 error. I can swap the URI with the URI from my old app and it functions, so I'm sure it's the new addon causing the problems. I've tried resetting the credentials and it did not fix the problem. I've also tried updating the packages
How do I get Channels to connect using a URI with no username? Can I force a username? Can I force an old version of Redis that has the username?
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.
Just getting started with laravel and have run into some trouble.
Before committing to using laravel I wanted to build a very basic web app to test the waters via homestead and then move that web app to a remote server in order to see how easy the process was.
So I've got homestead up and running and have built a very basic web app and it works perfectly locally.
However when I moved the laravel project onto the remote server the routing stopped working.
For example locally testProject.dev/contact takes me through to a mock 'contact us' view. However when I try that on productionServer.com/contact I'm greeted by a 403 'you do not have permission to access contact on this server'.
Am I missing something in laravel here or is this an issue with the sever setup?
Any help would be greatly appreciated. Thanks
Update -> This turned out to be an issue with another piece of software running on the server. Thanks for all the help.