Closed kaaax0815 closed 1 month ago
Nxssie
commented
1 month ago Hi, I have a similar issue, all deployed fine in localhost but no response in public network, port forwarding done, firewall rules done, even tried with docker net host to simplify and remove nodes of errors. Still offline.
I'm using wsl2 backend in docker, wsl have ufw enabled with ports open too, so tried everything that came to mind and not working.
wolveix
commented
1 month ago Hi both. This is not a container issue, please seek support in the official Satisfactory Discord. There is a networking issue somewhere within your setup.
Please keep in mind that within your local network, you'll need to use your server's local IP, and not your external IP. Yes, I know this should work, but it generally doesn't for Satisfactory.
kaaax0815
commented
1 month ago Hi both. This is not a container issue, please seek support in the official Satisfactory Discord. There is a networking issue somewhere within your setup.
Highly doubt this is a networking issue on my setup as other servers work just fine
Please keep in mind that within your local network, you'll need to use your server's local IP, and not your external IP. Yes, I know this should work, but it generally doesn't for Satisfactory.
Not a problem here. As I am not in the Servers network and am using its Public IP
wolveix
commented
1 month ago @kaaax0815 you may be correct; however, since 1.0 released I've helped hundreds of people on the Satisfactory Discord who are always just as certain. Every single time, it was indeed a networking issue.
I'll happily help you figure it out, but I need the full issue template filled out, otherwise it's a lot of back and forth asking for that same information :)
kaaax0815
commented
1 month ago @wolveix I would really appreciate your help. I filled to issue template to best of my knowledge. If anything is missing I'll swiftly update it
wolveix
commented
1 month ago @kaaax0815 the most important part is the Docker run/compose information, which hasn't been supplied. It looks like you mixed up a few sections of the template :) Please edit the original post with the missing information, and I'll see if anytging obvious stands out!
kaaax0815
commented
1 month ago @kaaax0815 the most important part is the Docker run/compose information, which hasn't been supplied.
My bad. I updated the issue
wolveix
commented
1 month ago Thanks @kaaax0815. I assume you're using IPv4, right? Could you send me your public IP for the server?
wolveix
commented
1 month ago For anyone else stumbling across this:
@kaaax0815 sent their IP via Discord, and I was able to connect to the server without issues. There appears to be a networking issue somewhere on their end, they suggested it could be due to them using WireGuard.
Describe the Bug
Started everything but appears as offline in Server Manager even tho I can't see any reason to why
Your Runtime Command or Docker Compose File
Please censor anything sensitive. Your runtime command might look like this:
Debug Output
Run the container with
DEBUG=trueas an environment variable, and it'll print out the system specs requested below, as well as a bunch of information about your container (version, environment variables, etc.)System Specs (please complete the following information):
If you're on Linux, just paste the following block as a single command, and paste the output here.
Logs
Additional Context
Firewall Rules are added
Dedicated Server so no Port Forwarding or similar needed (other servers work fine)