SplitHoirzon
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by SplitHoirzon
-
-
Im hoping you all have an answer to this. I had to delete my Docker.img and re-install all my docker containers. Everything is great but SWAG. Every time it tried to get a cert it says Connection refused on all connections. I have had SWAG and its predecessor running for years with no problems. I have troubleshot it for 2 days and found that whatever ports I assign to the SWAG container refuse connection. I can try it on my LAN taking the firewall out of the equation and get the same results. I have assigned multiple ports to the container and it refuses them. I can put the same ports on other containers and they work fine. I have tried it on proxynet, Host, and Br0 networks and same results. Just for some reason SWAG refuses any connection. Im desperate for help.
-
Im having the problem with the spinner never going away and my CA never loads. Here are my Debug logs.
-
Awesome thanks, Got everything fixed. Really appreciate it!!!!
-
7 hours ago, johnnie.black said:
Cache should be re-formatted, backup data, format and restore (docker image is also corrupt, but formatting cache will recreate it)
Ok, thanks. Thats what I have done and I am setting up the containers again. Just out of curiosity is there a way to backup container settings so I don't have to go back and manually do all the settings for each container? I backed up and restored appdata it's just the container settings I don't have backed up
-
I ran btrfs check and this was the results.
[1/7] checking root items [2/7] checking extents data backref 798845112320 root 5 owner 5589946 offset 13557760 num_refs 0 not found in extent tree incorrect local backref count on 798845112320 root 5 owner 5589946 offset 13557760 found 1 wanted 0 back 0x75116f0 incorrect local backref count on 798845112320 root 5 owner 5589946 offset 4611686018440945664 found 0 wanted 1 back 0x9d990b0 backref disk bytenr does not match extent record, bytenr=798845112320, ref bytenr=0 backpointer mismatch on [798845112320 12288] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space cache [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdg1 UUID: 25ded935-dbfe-47ac-93be-6cef80df1dc1 found 328026427392 bytes used, error(s) found total csum bytes: 175396908 total tree bytes: 1422508032 total fs tree bytes: 1102987264 total extent tree bytes: 108199936 btree space waste bytes: 284412128 file data blocks allocated: 2072377905152 referenced 309346455552
-
I updated to Version: 6.7.0-rc7 through the NVIDIA plugin today and also installed my license key. Upon reboot my Cache drive is in Read Only and I can't start any of the Containers or VMs.
-
I just deleted it. Not worth the trouble. I'll stick with Krusader. Thanks anyway
-
I installed it. Ran it for the first time. It asked me to log in. I googled it found the admin/admin. Tried it multiple times and it never lets me in
s it running? yes
Any Infos in the log file?
log just says
2019/03/21 17:17:53 Using config file: /.filebrowser.json
2019/03/21 17:17:53 Listening on [::]:80Did you mount the db correctly?
yep
-
I just installed FileBrowser for the first time and admin/admin doesn't work for me
-
8 hours ago, j0nnymoe said:
Nothing - the latest tag hasn't been updated yet. https://hub.docker.com/r/emby/embyserver/tags
When can we expect this? I was having the same question and glad I am not doing anything wrong. Im just curious
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
in Docker Containers
Posted · Edited by SplitHoirzon
OK i had an inspiration as soon as I posted this. I was correct as the container was refusing the connection itself. I didnt go far enough. When I reinstalled SWAG I used the "previous apps' section and reinstalled it with all my old settings. For some reason when the container, the premade port inside the container that is greyed out and cannot be changed was assigned http 185:180 and https 1445:1443. So basically I had to delete those setting and create then from scratch using the correct internal of 80:180 and 443:1443. I have no idea why the template did this but its fixed and working.