ich777

Community Developer
  • Posts

    14591
  • Joined

  • Last visited

  • Days Won

    185

Everything posted by ich777

  1. Answered multiple times (read the full linked post) :
  2. I haven't had got time yet but I think will have some spare time today and report back, the container is already installed on my server for testing.
  3. If you have a domain assigned to your public IP you just can give people your domain name and people can then connect through your domain instead of your public IP in game at direct connection, they just have to replace 127.0.0.1 with yourdomain.com in game so that it looks something like that: yourdomain.com:8211 The game then will resolve your IP with the domain and people can connect (you don't have to use a subdomain since this will complicate things for people further) Please note that this currently will only work if you have made a non community server as described here otherwise they have to search your server in the server list (which is I think still currently borked I think).
  4. Are you sure that you are not behind a CG-NAT? You can change this to true in the Docker template and it will obtain your public IP on every start which is also displayed in the log from the container:
  5. Yes, this was in their documentation right at the beginning, maybe it was listed their wrong. You can change it if you want to, as you know my containers are usually pretty good if you want to customize them (at least I hope that that's the case). I change it so that the new parameters apply to new installations, hope they cause no harm.
  6. Just try OPNsense, it's a bit more user friendly, looks similar but you also have to configure Hair Pin NAT but it is way easier and there are much tutorials out there for OPNsense.
  7. To your domain, not subdomain, don't know why would use a subdomain because the game needs to just resolve your domain to get your IP address. To your public IP address from your server, the server must be directly reachable through this IP from the outside world. Also look at this post from @Nodiaque: BTW, the container obtains your IP on the first container start automatically.
  8. Don't know if I can... This seems to be Alder Lake P mobile chip, please execute this from a Unraid terminal and reboot afterwards: mkdir -p /boot/config/modprobe.d echo "options i915 enable_guc=3" > /boot/config/modprobe.d/i915.conf If that doesn't work please provide a bit more information about your setup, what Docker container, a screenshot from the Docker template, did you do the necessary steps for Plex with the Claim?
  9. Then something is missconfigured in your network. For pfSense look here. If it's not configured properly then it won't work from your LAN but friends can join usually through your public IP or server list.
  10. Download spigot, put the jar file in the main directory from the container and change this values: It should be pretty self explanatory when you read the description from the variables. Of course you have to change the Serverfile name to whatever your spigot file is named to.
  11. What error do they get? I'm also not with that little information. Double check your port forwarding if the port is correct and if the protocol matches.
  12. Yes, simply forward the Port 8211 UDP in your router and you should be good to go.
  13. Maybe try OPNsense, works also pretty well and is (at least in my opinion) more user friendly <- but you also have to configure OPNsense/PFsense for Hair Pin NAT.
  14. Did you test this from outside your LAN or did you try it from inside your LAN. For a few users Hair Pin NAT is not working correctly on their network hardware and they can only connect with their local IP when they are in their LAN. When using the default bridge (which I btw recommend) you just forward UNRAIDIP:PORT in your router in your LAN and the same port on your WAN but no or all IP addresses on the WAN <- this depends on the manufacturer since no address means for most routers all IP addresses. But as said most of the times it is just that the Hair Pin NAT is not working correctly. Maybe ask someone if he can connect to your IP address or server from outside your LAN. Do you have other services available that are reachable from the outside world?
  15. Oh, that's a bummer, but glad that you've figured it out.
  16. Maybe try Unraid... You know that you can also set up a small box with a Trail license (30-days and 2x 15 days extension period <- so to speak 60 days). Sorry for being not more helpful here but in my opinion this can only be a permission issue. Something feels very off here... Have you yet tried to ask in the TrueNAS forums? May I ask if you have to use volumes or bind mounts on TrueNAS, I've never run a container with a volume, I only use bind mounts.
  17. Your public IP is gathered from ipv4.icanhazip.com on the first start and/or if the Public IP check in the template is enabled. (The public IP check is in my container since the release from the container since connections from community servers won't work properly if the public IP is not in place) Because you've terminated the container or at least you've stopped it, there is nothing I can do about that message, that message is always displayed when you stop or restart the container. Is something not working or what is the exact issue now? If the container is not restarting it is usually running and waiting for connections.
  18. Are you really sure that the files where they should belong and that everything is set up as it should be since I just changed a setting on my server in the ini and it is just working fine and applied the setting that I've changed. Something is certainly wrong. Did you also stop the container when invoking the mover? You could also try to change the path to /mnt/user/appdata/... but you have to make sure that you just have one copy of the ini file.
  19. I don't see a iGPU in your lspci output, did you change something in terms of hardware or did you made any changes in the BIOS or upgraded the BIOS? Please keep in mind that you have to enable Multi Monitor support in the BIOS to keep the iGPU active if you have a dGPU installed <- at least that's the case for most motherboards.
  20. I would always recommend stopping the container in the first place, then change whatever you like and then start it up again. There a few dedicated server which are the same as Palworld and they actually save the current config again when shutting down the game server <- which is basically done on a restart. Not all game servers are the same and they all of course are using different Engines.
  21. I will look into that but my day just started so you have to wait a bit until I got home from work.
  22. Your Diagnostics are missing from the post which are needed for troubleshooting.
  23. Do you have other services reachable from outside? I can try this later today on my server when I got home from work if you want me to do that. Please also double check your port forward and if the protocol is correct.
  24. Sorry no, this is not the same problem. Please read this here: