Experiment626

Members
  • Posts

    3
  • Joined

  • Last visited

Experiment626's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Oh it does. But. (and this is a big but). This is the default: It'll start fine with the defaults on install. (1880, 18443). Now, if I change http/https to 80/443, it barfs. Because Unraid itself is already using those. It would be fine to live on the default ports, if I was using IPv4 only. The problem lies with ipv6. Because you don't forward ipv6 ports (at least I don't, native /56 network to play with).. then https (v6) = 18443, not the expected 443. There's no network translation, therefore no port forwarding. Therefore having ipv6 on anything *other* than 80/443 isn't an option. So, the way to get around that, is use something other than bridge. But the config won't do custom ports that way. It forces me to use the defined ports only. So I'm back to square 1. Can't use v6 with the docker.
  2. Is there a technical reason why the variables don't work in Custom? I did experiment with this docker. In bridge it wouldn't start (obviously, unraid itself is already using 80/443). So I set custom, but that barfs horribly when it comes to ipv6. Works fine for v4 (because my router portforwards for 4), but because I have native v6, it goes straight to the docker, expects 443, and it's not there. Its open on 4443. I'd suggest opening up 80/443 for use in Custom networks as well.
  3. Don't change things inside defaultgame/defaultgameusersettings.ini for starters. Shootergame/saved/config/linuxserver/game.ini (or the same path for gus.ini) is where you should do such things.