aptalca
-
Posts
3,064 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by aptalca
-
-
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).
-
1 hour ago, hardaur said:
It's looking for an MD5 hash of the password (in the config), not the password itself. Can generate one here: https://www.md5hashgenerator.com/
G
or use the command in the readme, linked in the template description: https://github.com/linuxserver/docker-boinc#application-setup
-
2 hours ago, dbinott said:
I have it working and it picked up my details from the online account (from old setup), but, when I open the Computing prefs window, it's blank. I guess not a huge deal since the properties can be update on their website.
Switch to advanced view, it's in the readme
-
1
-
-
2 hours ago, admsteck said:
Is it possible to remove the user/password prompt?
Yes, in the template, hit remove next to the variable. If you try to blank it out, it will default to abc/abc
-
2
-
-
4 hours ago, sjaak said:
i still use your docker app to control the other boinc images
and its working fine, its does not doing boinc work itself, only controlling the other.
oh yeah, sure, you can use that manager to connect to other clients. I hadn't thought of that.
-
8 minutes ago, Blairwin said:
I get this issue when I launch the docker and sign in to the web gui. Everything at default and I see cpu usage so it looks like it's running. Any reason why i just get stuck on this and can't connect?
Please post the docker log to pastebin and drop a link here
Did you wait for some time for it to connect?
-
Hey guys, just created the template for the new linuxserver boinc image, it should show up in CA soon. Here's the support thread:
As I said before, this one is new. It contains both the client and the manager, so no need to install anything on a different machine.
It supports gpu (although rosetta@home is currently not handing out gpu jobs, some of the other projects do).
Also, this one is multi-arch, so feel free to put any raspberry pis or other iot devices to use as well 😉
@squid when this is listed in CA, feel free to deprecate my old RDP Boinc one
-
2
-
1
-
-
6 hours ago, ghstridr said:
Need a little help. I updated to the linuxserverio Unraid 6.8.3. Main logs and console complain that the nvidia driver couldn't connect to my 1660TI and it thought that another driver was grabbing it. I do have virtio grabbing the card for when I have a Win10 vm booted. Is there anyway to get this to share between them or get virtio to talk to the nvidia driver in a proxy sort of way?
The first post explains it. You can't use the same gpu with docker and vm at the same time. VMs require exclusive access
-
1 hour ago, oeci said:
Guys, I'm at a complete loss here. On my Unraid server I've got a working nextcloud container plus a working letsencrypt container (for ports see screenshot). Nextcloud can be reached if I use the internal IP and over the subdomain bodenwiesli.duckdns.org I can reach the nginx server which tells me that the subdomain works and the port forwarding of the router is also active. But not matter what guide I follow (this one, this one or this one) it never works. I would really appreciate if someone could tell me how I need to configure the containers to get this working.
By the way for testing purposes I forwarded incoming requests to port 80 to the nextcloud container and was able to login to my nextcloud account so I'm 100 % positive that both the subdomain and the nextcloud container actually work. But I'm not ok with unencrypted traffic.
You're not using our nextcloud image
-
17 hours ago, kbbeer said:
Going down a rabbit hole this morning, curious if a solution exists to this problem. I've been using this container to allow access to one subdomain externally. I noticed today that if I go to my public ip (when remote) chrome prompts with a privacy error and gives the reason that this ip and the subdomain certs which I setup are different. Is it possible to configure so that my ip doesn't respond and you need to hit the subdomain for a response? Or is it best to create a cert for the main page to camouflage the subdomain?
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
-
12 hours ago, Squid said:
Any word on the template? (Or is it in a different repository than all the other containers?)
Our resident template maker is currently busy saving lives (literally, at the hospital) so no template yet. I'll see if I can put something together in the morning
-
15 minutes ago, ksculland said:
Cannot get the webUI to display
http://192.168.1.40:8097/#/client/c/Boinc
Is there anything I do?
Anything need be done on my router to allow this to work?
Try putting the config folder on /mnt/cache
-
Or you can ask your isp to stop blocking port 443. It worked for some people
-
1 hour ago, Hoopster said:
It crashed mine as well.
After ~2 hours running RDP-BOINC on my server (just installed today on main server), the GUI, SSH, Telnet, etc. all became unavailable. I think BIONC was still doing its thing as the server was still running and I could hear the CPU fan running on high. However, it was completely inaccessible and I had to hard reboot the server and cancel the resulting parity check.
Either don't set it to 100%, or make it run on all cores except for the 0. Unraid has a tendency to be unresponsive when other tasks push all cores to 100%
-
4
-
-
1 hour ago, luizmont said:
@aptalca I have confirmed that my ISP blocks port 80 and 443 (consumer connection).
From what I have read, the only way to use letsencrypt is with DNS challenges.
Is that correct? Can you help me to configure it? Or at least point me in the direction to do this....
Thank you very much!
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
-
Hey guys, here's an updated boinc docker image: https://hub.docker.com/r/linuxserver/boinc
It's brand spanking new, based on ubuntu bionic. Contains both the boinc client and manager, so no need to install anything on another machine. It's not suitable for an in-place upgrade from my old rdp-boinc image, but setting it up from scratch takes only a minute or two.
This one works with intel and nvidia (with the nvidia plugin) gpus (as long as the project supports it).
There will be a template and a support thread soon, but until then, you can just create it with the vars from the dockerhub description.
-
5
-
1
-
-
31 minutes ago, xthursdayx said:
Thanks for getting on it so quickly!
It's working for me as well.
Let us know when/if you push it to linuxserver/boinc.It's merged, currently building: https://ci.linuxserver.io/blue/organizations/jenkins/Docker-Pipeline-Builders%2Fdocker-boinc/detail/master/4/pipeline
-
40 minutes ago, J.Nerdy said:
Does Rosetta@home leverage the gpu?
Not sure. I tested seti@home because it advertised gpu with both Intel and nvidia.
-
5 hours ago, xthursdayx said:
Cool, thanks a lot. I don't know if it would be possible, but perhaps hurricane/dockergui:xvnc could just be swapped for lsiobase/guacgui (which, as you probably remember, was updated to bionic by @hurricanehrndz last year).
Here it is, wip. https://github.com/linuxserver/docker-boinc/tree/initial
Currently pushed to lsiodev/boinc
Tested with nvidia, it works (seti@home). I didn't have enough time to test igpu
-
2
-
-
2 hours ago, xthursdayx said:
@aptalca any chance of updating the RDP-BOINC container to the latest recommended version of BOINC? Right now the Dockerfile is pulling version 7.2.42 but the recommended version is 7.4.22. If you'd prefer, I'm happy to submit a PR to update the Dockerfile. Cheers.
That base is too old. I'll look into creating a new boinc image when I get a chance, on a newer base and perhaps with gpu support
-
3
-
1
-
-
10 hours ago, luizmont said:
Thanks for trying to help me!
So, I believe I know the basics of port forwarding, and because of that (only the basics) I don't know what might be wrong in my setup...
Yeah, I understand that... And I can't access the nginx default page on my cell...
It gives the time out error.
Can you elaborate on this part?
I think nginx is starting, because I can access it from LAN.
These are my port forward rules
And my docker setup
I can provide more screenshots or logs if needed.
Edit: adding a diagram of my network
In your previous post, you posted port forwarding on an asus router, now pfsense. Are you double natting?
-
1 hour ago, scubieman said:
What information do you need? I followed space invaders video. I guess I did something wrong.
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.
-
On 3/13/2020 at 1:41 PM, frodr said:
Do:
"During first login, make sure that the "Authentication" in the webui is set to "Local" instead of "PAM". Then set up the user accounts with their passwords (user accounts created under PAM do not survive container update or recreation)"
mean that "admin" should be removed in the url logon?:
https://XX.XX.XX.XX:943/admin/
If so I arrive here:
Going to "Admin" I get this url:
https://XX.XX.XX.XX:943/admin/
Loggin in with default PAM I get this annoying guy:
I have a feeling I am doing something wrong (after 2 hours)...........
Can it be port forwarding? 1194 to 943 on server ip.
Anyone?
//Frode
See here: https://discourse.linuxserver.io/t/just-installed-openvpn-as-cant-login-as-admin/1162/5
[Support] Linuxserver.io - Folding@home
in Docker Containers
Posted
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.