Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When changing .env file to point to a remote Postgres instance example not working #465

Open
alexbegun opened this issue Nov 27, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@alexbegun
Copy link

When running this example locally everything works fine, but as soon as I change the
PG.HOST=XXX.XXX.XXX.XXX to a remote postgres instance the example still trys to connect to the local instance.

@robjtede
Copy link
Member

Might just be running it from the wrong directory.

Can you provide a more complete set of reproduction steps?

@alexbegun
Copy link
Author

So my regular test my env file looks exactly the same as the example:

SERVER_ADDR=127.0.0.1:80
PG.USER=tester
PG.PASSWORD=tester
PG.HOST=127.0.0.1
PG.PORT=5432
PG.DBNAME=testing_db
PG.POOL.MAX_SIZE=16

I do a post to 127.0.0.1:80/users with

{
"email":"[email protected]",
"first_name":"test_f",
"last_name":"test_l",
"username":"test12"
}

and everything works fine. The record gets inserted into my local Postgres database.

Then I installed a remote instance of Postgres onto the Microsoft Azure Cloud environment and changed
PG.HOST=127.0.0.1 to point to the Microsoft Cloud Postgres IP address. I made sure to set the security policy to be able to connect,
I proved that I can by running pgAdmin 4 and connecting to the remote Postgres Instance.

Upon changing the PG.HOST, When I run my code it seems like it doesnt even use the PG.HOST setting. It always goes locally regardless of what PG.HOST is set to.

I can prove this because when I have the PG.HOST point to the remote Postgres instance and I shut down my local postgres instance I get :

An error occured while creating a new object: error connecting to server: No connection could be made because the target machine actively refused it. (os error 10061)

@robjtede robjtede added the bug Something isn't working label Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants