Cybernaut

Thanks! That worked for my issue of running a second instance.

That doesn't appear to be it. As well as trying another browser, I couldn't telent to it. I could to the original on 8080.

I'm trying to get a 2nd qbittorrentvpn client up and running. Actually, it may be running, but I can't access the gui to tell for sure. The log doesn't show any errors, and the container is started. I suppose there's a way to tell for sure from the console. Anyway, I tried to copy the config from the first (working) container, and just change the conflicting host ports and DL folder. The configs are a little different when I go to edit, though. The original has host port 1, 2, 3, 4, key 1, etc. The new one has names for all those. When I try to open the container, I get a message that the site can't be reached. I suspect it's something simple with the ports. Can anyone help me out? original container Host Port 1: 6881 Container Port: 6881 Host Port 2: 6881 Container Port: 6881 Host Port 3: 8080 Container Port: 8080 Host Port 4: 8118 Container Port: 8118 Key 9: 8080 Container Variable: WEBUI_PORT New Container Port: Web Interface: 8082 Container Port: 8080 Port: Privoxy: 8120 Container Port: 8118 Variable: WEBUI_PORT: 8082 Container Variable: WEBUI_PORT

Same thing gonna happen with binhex-sabnzbdvpn?

Hey! You're out line with that common sense stuff! Take it somewhere else!

Hmmm...My pfSense dashboard doesn't revert back to default every time the cookies are deleted. They seem to have found a way to make it work. At the very least, they should warn you when you're customizing it, that it's temporary.

Nicely done! I upgraded from the Fractal 304 to the 804 about 3 years ago. I love that it fits in my desk after I removed the drawer hardware!

+1 For me, it's 6 of 14 containers on a custom network (if that matters). I was a couple updates behind. Updated to 6.12.6 to see if that would fix it, to no avail.

Hi. I've got the X-Robots-Tag issue. I've been reading and trying things for a couple days, but when I put "noindex, nofollow" in default.conf, i cant open NextCloud. I get a bad gateway error 502 when trying to access via my domain, and ERR_CONNECTION_TIMED_OUT trying to open on the local network. I'm guessing it's because I go through SWAG. Is there something I need to configure in there?

Hi folks. I'm having a problem where nothing displays in the panes below the menu bar - even if I click on menu bar items, the list does not display into that area. It's been fine on my home network, but the problem occurs when outside my network. I'm away from home and can't check the version I'm on, but it auto updates weekly. I also use SWAG with my own domain at Cloudfare. I have other containers going through SWAG/Cloudflare without issue. I also use NZB360 and can verify there are a couple dozen active torrents. Anyone seen this or know of a fix?

I'm sure you've tried selecting "yes" for allow remote access, and checking that the port is open? I'm no expert, but seems like that should be set to yes. BTW - I found this because I'm also showing offline. I logged out and back in via the plugin like you mentioned, and now I'm showing online. We'll see for how long.

Hi Folks. I apologize it this has already been addressed. I've been searching for a couple hours, and frankly, I haven't read this 238 page thread. I started receiving emails saying my letsencrypt certs are about to expire. Delving into it, it looks like the last log I have in the appdata/swag/log/letsencrypt folders is dated 11/23/22 (below). It looks like the cron job is no longer running? Appreciate any help. cronjob running on Wed Nov 23 02:08:00 MST 2022 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/my.domain.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Certificate not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certificates are not due for renewal yet: /etc/letsencrypt/live/my.domain/fullchain.pem expires on 2023-02-13 (skipped) No renewals were attempted. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Anyone having an issue updating Docker containers? I get the white box saying updating containers with the green bouncing circles at the bottom that never seems to complete. I just updated swag, got the box, went out and mowed the lawn, came back and it was still going. Refreshing the page, it looks like it successfully updated. Tried it again, this time updating all, and same thing. Brave browser and docker folders installed, if that makes a difference.

I'm no expert. Trying to get mine working too. But, did you do this; "The container is looking for 3 files that are missing which are referenced in the default 'unbound.conf' file that was placed there. You can download/create the missing 'a-records.conf', 'forward-records.conf', and 'srv-records.conf' files. https://github.com/MatthewVance/unbound-docker/tree/master/1.10.1 The github repository (version 1.10.1 is the current version at the time of this writing) has the 3 files you need. Just go into each file and Right-Click the Raw button and Save As in order to download the 3 files. Copy them into the appdata/unbound folder and restart the container." Pay attention to the "right click in Raw" I chased my tail for a while before realizing I'd DL'ed the html version.

So, I never did figure out why Nextcloud moved/deleted so many of my files. It seems to have moved a bunch to the userprofile\files folder of the Nextcloud share, and deleted a bunch that went to the pruserprofile\files_trashbin\files folder. I would start a restore from Nextcloud trashbin, and my laptop fans would spin up and the browser would freeze for several minutes. It would end up restoring 500 to 1000 files before stopping. It seemed to be using the browsers resources, so I moved to my desktop. Worked a little better, and after many tries, finally got all those restored. It took a couple days of going through the userprofile\files files and manually moving them back where they belonged, but finally done. In the end, I don't think it was an unraid issue, but appreciated those who helped me get things restored.