zanion
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by zanion
-
-
19 hours ago, saarg said:
You don't own duckdns, do you? You have to set the domain to whatever username you created at duckdns also. Not only duckdns.org.
I get the same problem if i do that, i have attached my configuration of swag. If i set only subdomain to true, then it will always look at the domain+subdomain as one unit. If i do as you suggest, then i have to set the only subdomain to false, then make my subdomain under the domain tab.
The problem is still the same.
-
hi, i got a problem while setting up this container.
I cant see the problem, i think it is something about the portforward. I just cannot figure out what.
I have attached the log form the docker menu, a screendump of my port forward and a screendump of my port assignment to the docker container.
I hope someone can help me getting this up and running
-
On 2/21/2020 at 8:35 PM, wedge22 said:
I upgraded to 6.8.2 yesterday and then Plex stopped working, I noticed I had the old depreceated version so I decided to follow the video by Spaceinvaderone and migrate to a newer supported Plex docker from Linuxserver team. I am still having the same issues with the new docker as the old one. I can login to Plex via the webgui, page loads erros for all my folders and shows cannot connect to server. I also tried another new installation without referencing any of the old Docker appdata and I get the "No soup for you error after webgui login".
i got the exact same problem. Plex will run as it should for like 10min after a full reboot of my unraid server. After the 10min then its dies again.
Anyone there got a fix to this problem?
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
in Docker Containers
Posted
ok, as i said in the post before, the problem is the same. I have tried to make the config as you suggest, and i got the same error.
I have made a check on the ports, they are open.
docker log swag rev. 1.txt