One user in Discord had their Generator spend its first days showing offline for two stacked reasons: port 8080 wasn't open publicly, and the registration app had auto-filled their Docker bridge IP (172.17.0.2) as the connection string instead of their public IP. Opening 8080 was the piece that got them online, but the bridge IP was a separate problem they'd hit at registration.
The dashboard reads the IP out of the registered connection string, so a bridge IP in there sends the probe nowhere no matter what the firewall says. Neither page covers it:
Related: #428 (open) is another Docker gap in the Generator docs, so the two could land together.
One user in Discord had their Generator spend its first days showing offline for two stacked reasons: port
8080wasn't open publicly, and the registration app had auto-filled their Docker bridge IP (172.17.0.2) as the connection string instead of their public IP. Opening8080was the piece that got them online, but the bridge IP was a separate problem they'd hit at registration.The dashboard reads the IP out of the registered connection string, so a bridge IP in there sends the probe nowhere no matter what the firewall says. Neither page covers it:
The register page lists Connection string as a field ("The endpoint operators and hosts will use to connect to your generator node") with no guidance on what belongs in it.
The troubleshooting entry "My Generator appears offline in the dashboard but is still running" is about the port being reachable, not about the registered IP being wrong.
In the register page's Registration step, tell Docker users to check the auto-filled connection string before submitting, and to swap the bridge IP for their public IP if it shows up.
Add the bridge IP as a second check in the offline troubleshooting entry, after the port.
Related: #428 (open) is another Docker gap in the Generator docs, so the two could land together.