Trouble setting up IPC KnownNetworks with Docker and Traefik #3534
Verified answer
by
JustArchi
rashedobaid
asked this question in
Support (English)
-
|
Hi, I’m trying to set up IPC.KnownNetworks for ArchiSteamFarm running in Docker, with Traefik as a reverse proxy, but I haven’t been able to get it working. 
Below is my current configuration. ASF.json IPC.config
|
Beta Was this translation helpful? Give feedback.
Admin verified this answer by
JustArchi
Jan 5, 2026
Replies: 2 comments 4 replies
-
|
Well you're definitely not loading the (Which on its own is ASF problem because it should gracefully error but otherwise continue to work, so I'll change this crash into an error, but that doesn't change the fact your IPC interface would not start at all, even if ASF did) So firstly evaluate why your config is not picked up, likely wrong location or stuff like that, and when ASF starts crashing then that'll be a sign it gets picked up, so that's when you fix it by removing invalid comment from it that you've added. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
My bad — I had only added a comment to the code block for reference and missed the JSON language, it wasn’t included in the actual configuration. I can confirm that Additional steps taken:
Directory tree |
Beta Was this translation helpful? Give feedback.
-
|
Running in debug mode Adding all LAN: |
Beta Was this translation helpful? Give feedback.
-
|
@rashedobaid I can't confirm what you're stating entirely. I started completely new instance of ASF on my LAN home server. As expected, I couldn't connect with it, because IPC is listening on localhost only initially. So I enabled access for all IPs (as per your config), then I could access ASF-ui there, but it complained about Then I added Most likely one of the following happens:
In second case, that's entirely intended, your web server properly informs ASF in As stated in the wiki, this mechanism is not something you should disregard, unless you entirely trust the networks you've specified. You're not in that network, you're accessing your machine remotely from external IP, the fact that your web server is within that network does not change that (as it executes requests on your behalf), which means the security mechanisms work as expected. If you want to shoot yourself in the foot, ASF allows doing that, but then don't complain one day somebody found your domain and stole your Steam accounts - this is why even though you configured everything properly, ASF still complains about |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Thanks for the detailed explanation, @JustArchi, and apologies for the lack of context earlier. After some more testing, things started working once I set I do understand and appreciate the security concerns you outlined. In my case, the environment is strictly LAN only, which is why I was initially confused by the complaint. My goal was simply to integrate ASF with my middleware running inside the same trusted network. Thanks again for taking the time to explain the intended behavior and the risks involved. |
Beta Was this translation helpful? Give feedback.
-
|
Great to hear that you've managed to resolve it. ASF checks for |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@rashedobaid I can't confirm what you're stating entirely.
I started completely new instance of ASF on my LAN home server. As expected, I couldn't connect with it, because IPC is listening on localhost only initially.
So I enabled access for all IPs (as per your config), then I could access ASF-ui there, but it complained about
IPCPasswordnot being set, once again, as expected, because that's additional security measure.Then I added
192.168.0.0/16(which is my LAN network) toKnownNetworks, restarted the instance and once again, as expected, I can now access whole ASF-ui withoutIPCPasswordset, it doesn't complain about anything anymore. This confirms the whole mechanism in ASF regardi…