No longer functional #756
Replies: 5 comments 5 replies
-
|
This looks like a normal start of the container. Do you have a port mapping in your |
Beta Was this translation helpful? Give feedback.
-
|
On first start it never came up (waited over 5mins after seeing that prior exit code 0) I tried again cleanly and perhaps on first start it needs time more than that - there was/is a big (>2min) delay between the 'application started' and it tendering a client connection. Didn't seem like a congestion issue - but forgive my impatience either way. |
Beta Was this translation helpful? Give feedback.
-
|
▒▓ │ ~/netbox-docker │ on release ▓▒░ docker logs 180501 ░▒▓ ✔ │ at 06:08:15 ▓▒░ |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Did you change the Nginx Unit configuration? If not why are you mapping the port to 8000? version: '3.4'
services:
netbox:
ports:
- 8000:8080 |
Beta Was this translation helpful? Give feedback.
-
|
I can´t believe! I did it because I am using port 8080. But it worked. Thanx |
Beta Was this translation helpful? Give feedback.
-
|
The first port (8000) is the "external port". That has to be unique for your host (or IP on the host). The second is the internal port where Nginx unit is providing the service. This one is isolated from your host ports by docker. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. I know, thank you. I was pretty confused because my host has: I need to use this netbox stack and it was a bit confusing in how to change these default ports in netbox and it's stacks. by the way, thanxx |
Beta Was this translation helpful? Give feedback.
-
Tried bringing this up multiple times - assuming it is abandoned. Netbox never comes up on any exposed port after successful init.
Suggest re-writing as deprecated in the instructions.
Beta Was this translation helpful? Give feedback.
All reactions