MrTroll

Hey man are you keeping this updated because I'm getting out of date or insecure errors?

I'm slow in the head mate didn't realised TF classic is the old one. Can you give me more info on how your containers work so I can try and edit the TF2 container to work with classified. If I change the game name and the steam ID it grabs the right files and everything but it never starts the server.

But its a container you already have? TF2C just updated to actually be on steam now!

Hey man tf2c is now fully launched on steam and has its own dedicated server app ID at 3557020. I've tried modifying your existing tf2 and tf2 c containers variables but keep running into start up loops. Seems like its not launching the srcds.sh properly the logs just loop the start-up routines.

I'm fairly certain all it takes is port forwarding. A mate of mine managed this with his and his mother's like you. I can ask him if you want homie.

11notes/unifi:9-unraid if you're down for any bugs that might crop up with a fresh release. Otherwise sub the number for the current version number of the "Network Server" on unifis website.

https://help.ui.com/hc/en-us/articles/115012240067-Enabling-UniFi-Remote-Management

It'll make it show up in the iOS app mate

Mate just run on remote access in the settings of the web UI.

@PeteAsking @bmartino1 Ultimately fixed the issue I was having by changing the container to host with everything else being the unraid default. I can finally remote access! Got the green globe and everything works!

Cannot download keep getting this error docker: error pulling image configuration: download failed after attempts=6: dial tcp 130.117.252.104:443: i/o timeout.

Turns out I had a remote PC sitting on the unraid connect website filling my notification log with unraid API started. After removing this for the equation everything is smooth as butter.

Wasn't asking you too boss if it fixes itself neat, but I've just resigned myself to using another browser.

So i've been running into this issue where the web ui will be completely unaccessible, with running /etc/rc.d/rc.nginx restart via ssh resolving the issue. I've attached diag logs from the last time it happened, just before I restarted nginx. Side note I read somewhere to /etc/rc.d/rc.emhttpd restart but when I run that in ssh I get -bash: /etc/rc.d/rc.emhttpd: No such file or directory. jarby-diagnostics-20250505-2003.zip

Installed on my system before you posted this after checking available tags. Works without any issues so far! Didn't resolve my odd Firefox bug though.