aptalca

https://www.tomshardware.com/news/folding-at-home-worlds-top-supercomputers-coronavirus-covid-19 https://cointelegraph.com/news/foldinghome-surpasses-400-000-users-amid-crypto-contribution

"almost mirror" != "the same" If you post exactly what you did, we can try and help. But if you say "I followed x video or guide for the most part", then we don't have a crystal ball.

502 means letsencrypt cannot reach deluge You likely have deluge in host networking, so change the address to point to unraid ip and port to the mapped port in your proxy conf

It's saying you referenced a file in your default conf but the file doesn't exist

I think their servers are getting overloaded. Way too many people started folding recently due to coronavirus (myself included).

It should say connecting to localhost. What settings are you using?

Rosetta@home on boinc is not handing out GPU jobs at the moment. If you add another like SETI@home, you'll see in the task list when a job is using the gpu

Another quirk, even if the user doesn't use nvidia runtime, or enable all the gpus, all nvidia gpus on the system are still detected, but they can't be started to fold. You'll see errors in the log. Don't be surprised.

Usually when the container restarts, it continuously tries to reload. Force refresh (shft+F5 or ctrl+F5) seems to take care of that one. But on one machine, I get an "empty response" from the site. On that machine, I have to use incognito (without cache or cookies). No idea why.

The web gui is a bit finnicky and refuses to open for me in a regular chrome window (perhaps a conflict with cookies?). I can open it in an incognito window, though. Just fyi

This one doesn't require any manual edits to the config.xml. By default, both the web gui and remote access via FAHControl on a different device allow all connections and there is no password. The built-in webserver provides very basic control (ie. GPUs are only active when set to Medium or higher) and its cache management is very finicky. If you have issues connecting, try an incognito window. For more fine grained control of individual devices, you can use the FAHControl app on a different device and connect remotely via port 36330 (no password).

or use the command in the readme, linked in the template description: https://github.com/linuxserver/docker-boinc#application-setup

Switch to advanced view, it's in the readme

Yes, in the template, hit remove next to the variable. If you try to blank it out, it will default to abc/abc

Please post the docker log to pastebin and drop a link here Did you wait for some time for it to connect?

You're not using our nextcloud image

You can set the main server block (the one that's defined as default) to serve a 404 or not even respond. So only the match for the subdomain will be displayed, any other request will go to the default block and get denied

Or you can ask your isp to stop blocking port 443. It worked for some people

You're already using dns validation, that's why nginx is coming up and reverse proxy works on your lan. If 80/443 are blocked, you'll have to use a different port to access So you'll forward 444 on the router and access https://domain.com:444

In your previous post, you posted port forwarding on an asus router, now pfsense. Are you double natting?

How you set it up. "I followed X video or guide" is not the least bit helpful. Like I said, you should be accessing it at the nextcloud subdomain, not the main url. Either you're not using the right address, or you set it up very differently than we suggest.

See here: https://discourse.linuxserver.io/t/just-installed-openvpn-as-cant-login-as-admin/1162/5

Recommending a completely different protocol is not very productive in a thread dedicated to openvpn-as. Plus, wireguard is more of an alternative to vanilla openvpn, not openvpn-as as it requires manual config via cli. Also, I happen to use wireguard and openvpn side by side as one acts as a backup to the other.

Nextcloud should be available at a subdomain like https://nextcloud.yoursubdomain.duckdns.org How did you try to set it up?

If you read the article I linked, you'll see that there is a recommended resource with a plethora of information on just port forwarding (portforward.com). Until you can reach the nginx default page on your domain via cell connection, reverse proxy won't work for you outside of the home. And if you're using http validation, letsencrypt container won't even start nginx as it won't be able to validate the cert.