saarg

Community Developer
  • Posts

    5374
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by saarg

  1. Fail2ban starts when the container starts. It's started in /etc/services.d/fail2ban/run
  2. The port is already in use. I guess you have modified some configs?
  3. That should be in the unraid log. Not sure what is happening. Could you post your docker run command?
  4. It's in the unraid log or the scrutiny docker log?
  5. That's the host port and not the one used in swag. Swag talks directly to the container using the container port. Post your docker run command.
  6. You just have to change the upstream_app variable from container name to the IP of the app you want to proxy.
  7. I thought about that, but wasn't sure if it messes up the external access.
  8. Nobody knows why the docs is set to host, as it doesn't need host. So it's safe to set it to bridge and port map 3000.
  9. Did you use the same custom bridge for librespeed as you use for swag?
  10. Not that this will help much, but might be good to back up important files. Hard to figure anything out with the info you have supplied.
  11. I read it as you used the IP locally. Your new router most likely doesn't support NAT hairpin or split DNS. That's what makes the domain work locally also.
  12. You need to set the IP in config.php if I remember correctly. Under the trusted domains array.
  13. For you, yes, but not for me. So you want me to use more of my time, so you can use less of yours, fixing your problem? Change the port in the proxy conf to 443 and create a custom docker network and set both swag and nextcloud to use that one.
  14. Why have you changed the port? There is nothing mentioned about it in the instructions. Leave it as it originally was. Post the docker run commands for both nextcloud and and swag.
  15. We don't use the linuxserver account for support. It's only there to start support threads. There are still some of us lurking around here, but for fast support, our discord server is the best place to get support. Or our discourse forum, but that one is not so busy. chbmb will not be back here.
  16. And that is not true either. We only pulled the plug for the Nvidia and dvb builds. That's all. @wayner Containers doesn't need to be built for unraid. You can use all containers from docker hub.
  17. It's hard to help when you don't supply any info. My wild guess, something is wrong.
  18. It's still operating. Working here without errors. Spoke too soon. Looks like it's not updating the IP for some reason.
  19. You have really messed up your template. You are missing half of it. No wonder you don't find your appdata, as it's not mapped to host.