Container XXXXXX didn't respond to HTTP pings on port: 5100, failing site start. See container logs for debugging about passwordpusher HOT 8 CLOSED

@pglombardo @jgudmundson-RETSD
Thank you both for the help!

Looks like it was truly related to the password that contained special characters.
When I previously tried to quote the password with the "double quotes", that did not work either.
I changed the pw to not contain any special chars and now the database migrated successfully, is populated with tables, the app service is running and data are retained after the app restart too! Lovely 🙂

from passwordpusher.

I restarted my service to see if there is an issue with the newest release build, but it seems fine.
2 questions.

1. On your PostgreSQL server do you have "Allow public access from any Azure service within Azure to this server" checked under networking?
2. On the Web App, under networking do you have any access restrictions defined under inbound traffic?

from passwordpusher.

I restarted my service to see if there is an issue with the newest release build, but it seems fine. 2 questions.

1. On your PostgreSQL server do you have "Allow public access from any Azure service within Azure to this server" checked under networking?
2. On the Web App, under networking do you have any access restrictions defined under inbound traffic?

Hi @jgudmundson-RETSD, thanks for helping out here.

1. yes, first I added there only the outbound IPs of the App Service but then I also tested with the "Allow public access from any Azure service within Azure to this server" checked.
2. No, there are no restrictions on inbound/outbound traffic of App Service. All features are Off.

Don't know what difference it makes if I use the B1 tier for App Service Plan and the Postgres is running on the following cheapest server config "Burstable, B1ms, 1 vCores, 2 GiB RAM, 32 GiB storage".

from passwordpusher.

That helps. The application can't parse or lookup the database connection specified in DATABASE_URL:

URI::InvalidURIError: bad URI(is not URI?)

Could it be that your real username or password have characters that conflict with the URI? Such as , :, @ or others?

If so you may need to quote those strings or replace them with their UUEncode equivalent (@ == %40, == %20).

from passwordpusher.

Hello @jnhrv, thanks for contributing to the Password Pusher community! We will respond as soon as possible.

from passwordpusher.

I'm also running on B1, and B1ms.
Did you check if the database is populated? on the DB site click connect, pick table, enter the password, run "\dt+".

from passwordpusher.

The database should automatically be migrated on container start.

In that screenshot, the line before states that the container exited which means a startup issue. The most likely culprit to this is a missing DATABASE_URL environment variable that points to your postgres database.

An example would be:

DATABASE_URL=postgresql://user:passwd@host:5432/database-name

Could you verify this?

Last point - if you get the container startup output that will tell us exactly what the problem is.

Logging is not enabled for this container. Please use https://aka.ms/linux-diagnostics to enable logging to see container logs here.

from passwordpusher.

@jgudmundson-RETSD
Looks like the database is not populated.
postgres=> \dt+ Did not find any relations.

@pglombardo I attached logs after I changed the App Service to the postgres:release image and set the DATABASE_URL again.
The DATABASE_URL has been always in place when I used the postgres image.

pwpush_azureAppService_logs.txt

from passwordpusher.