Closed iamdavidfrancis closed 7 years ago
Hm. That's strange. It's never had an index.html, so I'm not sure why it's complaining now. I'm running it locally, and if I hit http://192.168.99.100
I get redirected to http://192.168.99.100/ui/relationships
. Can you hit the ui/relationships path?
Are you running something in front of it that is trying to hit robots, favicon and index?
The browser will automatically hit favicon and index, not sure about robots.
ui/relationships also returns a 404
That robots933456.txt
request looks really suspicious.
Are there any other errors in the logs? None of those errors explain why you're getting 404 for paths that actually should exist.
No, there's nothing else.
How are you running it?
It's running on an Azure App Service on Linux instance
Does that mean it's publicly accessible? That would explain the suspicious looking traffic.
On Wed, May 24, 2017 at 10:11 AM, David Francis notifications@github.com wrote:
It's running on an Azure App Service instance
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/DiUS/pact_broker-docker/issues/35#issuecomment-303576687, or mute the thread https://github.com/notifications/unsubscribe-auth/AADSjMTIxcMhvoIlAkcCtFZhajw4UlEEks5r83W6gaJpZM4NkTDE .
-- Matt Fellows
Yes, it's publicly accessible, but the robots file is being requested every time index.html is.
I'd say you need to look to the Azure docs for help.
I've been through them. I was hoping you might have some more information that could help me. It's alright if you can't, I'll keep looking.
What happens if you docker exec into the container and curl http://localhost
?
Okay, I figured out the problem. We had the wrong IP whitelisted on the postgres server. It's working now.
Thanks for the help though.
👍
Hi, I'm trying to get the pact broker working, but when I run the container I get a 404 page from nginx. I would appreciate some guidance on this.
I've attached part of the logs: