-
Posts
34 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by goodGame
-
-
27 minutes ago, Squid said:
Not really.... Trouble is that I've got no problems. The plugin gathers it's information from what Unraid itself. I could diagnose via some scripts etc, but not particularly feasible for me to do this until week of Aug 2nd after the flying coffin (hopefully) gets me back home from a "if you can't laugh you have to cry" installation for work.
PM me that week, as I will definitely forget all about this.
Will do, thanks
-
I have a weird issue where my letsencrypt docker container is not showing up in CA auto update. The container updates and behaves normally and as expected fine in the docker Tab. But it's as if it's not installed when I go to CA auto update.
Tried reinstalling the container and the plugin without luck. Any hints?
-
I like how you can get so many advanced features going so easy and easy to maintain. Meanwhile, if you want to get your hands dirty, there's no stopping if you want to do it your way and get your hands dirty (allmost).
I'd like VM snapshots for 2020! -
2 hours ago, strike said:
Re-fraising a bit. Yes, you do need an incoming port, but since you're using PIA you don't have to worry about that, this container does it for you. All you need to do is the 2 things I mentioned. 1. Make sure you have strict port forwarding enabled and 2. connect to a supported endpoint. But you said you confirmed that you got an incoming port in the logs, so that should all be ok.
The reason an open incoming port is important is that if you don't have that, nobody can connect to you and thus you can't upload anything. But your issue seems to be something else since you do have an open incoming port. Have you checked your private tracker? What does it say? The site may have an indication if your "connectable" or not.
How do you add you torrents do deluge?
I'm sorry to have wasted your time but I actually believe all is working well now. I've gotten stuff to seed now and I believe my issue was not seeding popular enough stuff... Sorry but thanks!
-
14 hours ago, strike said:
You do need an open incoming port, but if you're using PIA this container does the port forwarding for you automatically. All you have to do is enable strict port forward in the container template and connect to a supported endpoint. Have you confirmed that you get an incoming port? Check the log. Also if you're on a private tracker make sure to disable peer exchange and dht in the deluge settings.
I'm a bit confused, I do use PIA. At first you say I need an open incoming port, then you say all I need to do is enable strict port forward in the container. So if I use PIA, I do not need an open incoming port, correct?
I get an incoming port in the container logs, yes. And that's the port I'm using for incoming in Deluge. The problem seems to be outgoing.
DHT is off. I can't find peer exchange in the settings but I turned all off so should be off.
I now do get a very small upload but it maxes out at like 100kb/s very rarely, which is abysmal. Down I get 20+MBit/s without issues.
-
I'm having trouble getting deluge to upload. I'm using PIA with Sweden (tried with german too) endpoint and download works great. No matter what I seem to do it will not upload however. Is there something I need to add?
If I understand correctly, I don't need to open any ports?
-
Oh my, that was it. I have over 90 tabs open in 3 browsers, didn't notice it. I really have to deal with my tabs somehow...
No clue how you figured that out but thank you alot
-
I tried to get help in the announcement thread but noone replied, not sure what to do so going to try here.
After updating to 6.6.3 this error pops up in my systemlog every 10 seconds.
Oct 27 13:10:47 unRAID nginx: 2018/10/27 13:10:47 [crit] 7464#7464: *622 connect() to unix:/var/tmp/letsencrypt.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.44, server: , request: "GET /dockerterminal/letsencrypt/ws HTTP/1.1", upstream: "http://unix:/var/tmp/letsencrypt.sock:/ws", host: "73ea33eb735ffe6b67133d3f0f2ea238f9dd96de.unraid.net"I reverted to 6.6.2 but it's the same thing.
I don't notice anything but it fills up the logfile if nothing else, any help?
Thanks
-
My systemlog spams this after updating
Oct 26 13:38:23 unRAID nginx: 2018/10/26 13:38:23 [crit] 7439#7439: *3076 connect() to unix:/var/tmp/letsencrypt.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.44, server: , request: "GET /dockerterminal/letsencrypt/ws HTTP/1.1", upstream: "http://unix:/var/tmp/letsencrypt.sock:/ws", host: "73ea33eb735ffe6b67133d3f0f2ea238f9dd96de.unraid.net"
What is this about? There is indeed no "/var/tmp/letsencrypt.sock" in my fs
-
I found it, nevermind!
root@unRAID:~# grep 'CONFIG_HZ=' /usr/src/linux-4.14.49-unRAID/.config CONFIG_HZ=1000 -
Hello, looking for some assistance!
I'm trying out hosting some game servers on Unraid. I've been trying to find the HZ var in the kernel but I can't find the kernel config in unraid. It's normally in /boot/config-'uname -r', where can I find it in unraid? (Specifically the 'CONFIG_HZ=')
Also, I'm not terribly good at Linux in general. Compiling my own kernel for this would be out of my league I think, is there any way I can change this setting in a easier way?
*Edit, another question. If I have a VM with kernel config_hz=500 and the host (unraid) running kernel config_hz=200, the VM would still be running at a max of 200, correct? Could I bypass this by passing through logical CPUs to the VM?
Thanks
-
Allright, I understood now what happened since /var/log was full
plugin: removing: community.applications.plg
No such package: /var/log/packages/community.applications-2018.04.08. Can't remove.
plugin: removed -
44 minutes ago, trurl said:
Your log space is completely full but it's not clear why, since syslog isn't that large. What else do you have in /var/log?
Apparently an atop log of 127M.......
Edit: It's from one day too, too big to open, I've deleted it
Edit 2: I opened /var/log/atop/atop_20180326 and it wasn't readable by a text editor. Anyone know what it is? How can I prevent this from happening without removing atop? atop comes from the Nerd Pack Plugin
Edit 3: Actually I'm just gonna remove atop, not worth it. Thanks for pointing me in the right direction, trurl!
-
On 4/3/2018 at 10:13 PM, speedyyellow said:
I updated the plugin earlier today and it all seems to have gone wrong. The update process apparently went well but after it completed the Apps tab had gone and the plugin didn't display correctly in the plugin list. I removed it and tried installing from the url in the first post but get the following:
No matter what I do I can't get the plugin installed. Any ideas?
I'm getting the exact same thing from the last CA update (18-04-08). I have not tried reinstalling it however.
Also, my logs seem to have ended on 08? Both the syslog and dockerlog? The server's been online 24/7
-
On 1/26/2018 at 1:08 AM, mrow said:
What about a Chromebook? There are quite a few RDP clients for ChromeOS.
I know absolutely nothing about ChromeOS but checked out a few and seems really good for my purpose! You sure there are rdp client software you can install in chromeOS?
-
7 hours ago, pwm said:
There are lots of suitable laptops. It's that to be suitable it will be a full laptop. Which means the laptop itself can handle most everyday tasks locally - it's only when you need to run software that consumes lots of RAM, lots of CPU power or lots of GPU power that it is meaningful for you to off-load the heavy machinery work to a back-end server.
Commercial thin-client terminals normally costs more than hobbyist-level laptops, with the main purpose not to be cheap to buy but to remove the need for local administration and the need for regular, local, hardware updates.
So in the end, it's best for you to go the "normal" route where you run most software locally on the laptop.
Yes, that's pretty much what I found, I meant suitable as in suitable for me, as in cheap.
Watching video would be one requirement, hence I thought about RDP. Gonna check out Remmina too, sounds sweet.
The thing about getting a used laptop is I'd like something slim and lightweight, hard to find I guess. New would be preferable..
Gonna search some more, great inputs all
-
Meeeeh, I'm giving up on this. There are no suitable laptops for the purpose.
-
Allright, I got this idea. My laptop died, hence I was looking around for replacements. But it then hit me I could set up a VM in unraid and use a thin client, why not?
Now... the whole thing about this would be to save some hard earned cash, so does anyone know of a suitable laptop to use for this? The only thing it would need is a good screen and a decent ac-nic I suppose?
Is there some sort of RDP client OS? I know there is, companys use them. Are they availible for non business uses? Some open source ones maybe?
-
8 minutes ago, bonienl said:
Not yet. 6.4 is close to release, but it will be something for 6.5.
Spinning this a bit further... The only thing I miss, coming from ESXi, except snapshots is vspheres awesomeness when it comes to handling cpu resources. Now I don't have any expectations like that of course but is there any planned work on improved automated cpu handling for virtualized systems, with numa etc, for future releases?
-
On 8/23/2017 at 11:46 AM, bonienl said:
Is there a need / wish to do cpu selection for Dockers similar to what is done for VMs?
Did this result in anything?
I just tried assigning cpus to dockers that are isolated cpus but it won't work. If I assign cpu 20-29 to a docker and those threads are isolated in the syslinux, it only uses cpu 20. As soon as I remove isolcpus the docker gets the specified 20-29.
-
16 minutes ago, GilbN said:
You were missing some parts
location /web { proxy_pass http://127.0.0.1:32400; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location /plex { proxy_pass http://127.0.0.1/web; }Missing what? proxy_set_header params is in proxy.conf
the location /plex is just a redirect to /web so shouldn't affect /web in any way. Correct?
-
2 hours ago, GilbN said:
I use this for plex:
SSO.conf
This worked for me too, thanks alot man. Any clue as to why /web won't work?
-
Looking for some help here, running this container successfully except for one thing.
Proxy works flawlessly for any locations but one, plex.
As soon as I setup the /web location in nginx the url to plex redirects without the port added. If my plex is on http://192.168.1.10:32400/web it redirects to http://192.68.1.10/web/index.html asking for my unraid login prompt, if I enter the unraid credentials I get a 404.
Any other location works as intended to the designated port.
I've been sitting hours and hours trying to find the error, I've tried multiple different configs, at the moment I'm running a complete default LE container install (reinstalled LE container from scratch, deleting all config files before new install), with only two locations added to the default file as following:
location /web { proxy_pass http://192.168.1.10:32400; include /config/nginx/proxy.conf; } location /radarr { proxy_pass http://192.168.1.10:7878; include /config/nginx/proxy.conf; }All other nginx configs is currently as default.
Radarr works as intended. Plex does not, I get redirected to http://192.68.1.10/web/index.html
Theres no caching issue, I'm trying 3 different browsers and clearing everything.
Connecting to plex directly works fine, no issues. I've tried using different ports for the LE container, no difference. I'm using unraid 6.3.5 so no ssl on unraid.
What is going on? It's as if it refuses to redirect to port 32400. I don't understand
Hotio v CA
in Lounge
Posted
May I suggest the apt approach, use repositories. You'll have one default heavily moderated repo the Squid way.
Next, you'll have a community developers repo, with Linuxservers, Hotios, binhex etc
Next, you'll have a unsigned repo where stuff like https://github.com/selfhosters/unRAID-CA-templates goes.
Lastly you'll have dockerhub repo
End users can add any repo they want in CA settings.
The non tinker confused users will only see it like Squid intends it for them.