• Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About aterfax

  • Rank


  • Gender

Recent Profile Visitors

922 profile views
  1. The SWAG docker uses certbot........ /mnt/usr/appdata/swag/KEYS/letsencrypt/ is a symlink - due to the way docker mounts things you are better avoiding trying to mount anything symlinked as the appropriate file pathing must exist in the container. If you mount the symlink it will point at things that do not exist within a given container which is why the method 1 below required you to mount the entire config folder - a bad practice. Mounting a symlink of a cert directly will work, but mounting directly from /mnt/usr/a
  2. You are familiar with the concept of the past I assume? Edit: Here are the docs you need, your certificate files are not in the keys folder:
  3. 1 - Yes these are paths. 2 - I added - naturally you need to have setup your CNAME / MX records and forward ports in your router/network gateway to the server. If you wish for the web GUI of also to be accessible externally you will also need to setup the correct reverse proxy with SWAG. I don't know what you mean by .config 3 - I blanked the folder in the screen shot as I do not want to share my domain name, but yes the subfolder with your domain name / subdomain name is where the PEM files should be if you have setup SWAG correctly to get SS
  4. I ended up mounting the default certificate files in the docker directly to the certificates from my letsencrypt docker: But as I mentioned further up in this thread you can also mount .well-known folders between your Poste IO and letsencrypt docker - this will not work if your domain has HSTS turned on with redirects to HTTPS (or this was the case with the version of letsencypt in the docker a while ago as it was reported here: )
  5. You have advanced view turned on, you can toggle this at the top right.
  6. I too would like these to be added however I have solved the problem elsewhere before:
  7. Many thanks for the explanation - I was not aware that certain things would have issues with the virtual paths as it were. The script for L4D you sent me works great and starts everything in a screen which is super. In terms of screen / tmux support for gameservers - I have gotten quite used to using which keeps each server console in its own tmux and has a robust logging setup and a lot of support for many game servers. The access to the console via SSH or if in a docker potentially via the Unraid or portainer console is certainly my preference to RCON given R
  8. I do mean over SSL - you can access your docker consoles from the docker page inside Unraid after all or in setups like mine I have access to all running dockers via a portainer instance being hosted with SSL protection. I was using /mnt/user/appdata/l4d2 before getting it working on the cache drive- is there a reason why you cannot run this from an appdata dir like all my other dockers? I really have no idea what could be causing a segfault in /mnt/user/appdata/l4d2 unless the file system is doing something whacky in the background with the cache. E.g. below:
  9. Very odd - I now seem to have it working ok but only when on the cache drive.... Edit - the ask for access via screen for server console is kinda agnostic of the server type - some things will not support rcon and rcon itself is an insecure protocol - I'd rather just login over SSL and deal with things via portainer or via Unraid docker console.
  10. Just purged the folder and reinstalled the app from the community apps plugin again today, same issue - I have been installing to /mnt/user/appdata/l4d2 rather than cache from the start - I am on Unraid 6.8.3 - I can try using my cache drive - pretty sure my appdata folder is set to prefer mode so I will swap that now and see if that helps. See logs: Update state (0x101) committing, progress: 58.67 (4812218723 / 8202656842) Update state (0x101) committing, progress: 58.68 (4813019123 / 8202656842) Update state (0x101) committing, progress: 58.69 (4814223871 / 8202656842) Updat
  11. More debug - Further debug log output - /serverdata/serverfiles/srcds_run: 1: /serverdata/serverfiles/srcds_run: gdb: not found WARNING: Please install gdb first. goto Server will auto-restart if there is a crash. Setting breakpad minidump AppID = 222860 Using breakpad crash handler Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit Segmentation fault Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem
  12. Ah right - could I recommend launching all servers inside a screen or a tmux as an enhancement? As for the error with left4dead - I purged and reinstalled twice leaving it to validate the second time and it resulted in the following (part of why I wanted the console): Add "-debug" to the /serverdata/serverfiles/srcds_run command line to generate a debug.log to help with solving this problem Thu 13 Aug 2020 10:48:24 PM BST: Server restart in 10 seconds Setting breakpad minidump AppID = 222860 Using breakpad crash handler Forcing breakpad minidump interfaces to load Looki
  13. Any of the source servers e.g. left4dead2 which now appears to be stuck in a bootloop.
  14. Does this docker have any support for accessing the running console of the game through screen or tmux? I cannot see any documented way to access the running console to run server commands?
  15. I might be wrong, but when I have set different UID and GID this does not seem to be respecting that. Edit: Looking at the files, the UID and GID are currently hardcoded in the dockerfile and I do not see anything in the start scripting to change from the default values of 99 and 100. So if you need to change this, you need to use the dockerfile and build the image yourself currently. Might be an improvement to add something to the built in start script to account for this. Many thanks @ich777