MulletBoy

I am having a similar issue to the person above me, I have the quassel-core docker running and can access it fine from the desktop client, but when using the quessel-web docker i input the login credentials and it just spins at "connecting" forever. In the quassel-core logs I can see the following 2024-03-30 18:47:14 [Info ] Client connected from 172.18.0.1 If I connect from my desktop client the logs show 2024-03-30 18:47:58 [Info ] Client connected from 192.168.1.10 2024-03-30 18:47:58 [Info ] Client 192.168.1.10 initialized and authenticated successfully as "username" (UserId: 1). im using identical credentials for both, but the web client never triggers the second authentication line in the logs (sucess or fail...) its like it just isnt pushing the full request through? any support on this would be appreciated, i suspect this is a pretty rarely used docker given how quiet this thread is...

Im seeing similar symptoms, extremely high CPU usage in the UNRAID dashboard, by very normal cpu usage when i run 'top' or 'htop' in terminal. Restarts didnt fix it for me, and upgrading the latest unraid did not fix it either. ( I went from 6.6.3 to 6.6.6). I am running standard stuff, plex, sonarr, couch potato, sabnzbd, letsencrypt (with some wordpress sites), mysql, mariadb, nextcloud, rutorrent, unifi, muximux. I have found the culprit in my case to be couchpotato, it is running the mover on my completed torrents folder on repeat erroneously.. as in copy completed torrent xyz to the library location leaving a copy in the completed folder (as it should for seeding), however then not remembering that its processed that file already, and just doing it again and again, cycling through all the files in the folder.... I havent figured out what is wrong with couchpotato or how to fix it yet, but at least i know what the issue is and disabling couchpotato docker for now has stopped the super high CPU usage.

Hey All So basically, I have a fish tank that I want to live stream to a website that I host. I have an unraid server which is running many dockers, including the Linuxserver LetsEncrypt docker which is my main webserver for various websites I host. I have 2 potential locations for the camera The best location has power but would need to use wifi for connectivity The alternative location has Ethernet (POE) and direct Power so is very flexible... but I would only use this if a wifi enabled camera is going to be too difficult/expensive/bad for other reasons I am looking for advice as to a good way of going about setting this up... ideally with minimal cost, and utilizing my unraid server + some dockers for the entire solution. Any ideas? Looking for software and hardware recommendations!

In the last week or so, this docker has stopped connecting to all my trackers that require HTTPS for the tracker announce URL's I have tried blowing it away entirely and rebuilding with no luck, the same torrents added to Linuxserver transmission or deluge dockers work perfectly, Any ideas?

Hey All So i successfully configured this docker to run reverse proxies for about 8 other dockers, they are all exposed (with a .htpasswd for access) over https on my duckdns domain pointing to my server. Super happy with it, thanks to many within this thread for various code snippets that helped me, and my working code is pasted below What I want to do now is host a public wordpress blog, can anyone give me some insight as to how to do this? So far I have installed apache docker (linuxservers.io) copied (unzipped) wordpress into a folder in the www folder installed the mysql docker (linuxserver.io) hit wordpress config page, configured it to use the mysql db wordpress is kinda locally now at 192.168.1.100:89 (via apache) so now i started some random config in the NGINX site-confs/default file that I have pasted below edit: solved my problem, here is how I did it unzipped wordpress into a folder called insertmydomain2.com the www folder of ngynx installed the mysql docker (linuxserver.io) used the mysql workbench tool to configure a 'wordpress' schema, and create a user that can access it configured my nginx default config file as per below pointed A record of the the domain i am using for this wordpress to my ip address hit my domain and boom, wordpress config page, easy mode from there i really have no idea what i am doing i figured this shit out with brute force, some copy paste and lots of reading through this forum # wordpress server running without https server { listen 80; server_name insertmydomain2.com; root /config/www/insertmydomain2.com; index index.html index.htm index.php; location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php5-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php5-fpm: #fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } location / { try_files $uri $uri/ /index.php?$args; } location ~ \.php$ { fastcgi_split_path_info ^(/)(/.*)$; } } # main server with most of my dockers running on https server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name mydomain1.com; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; #muximux location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:99; } #sonarr location ^~ /sonarr { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:8989/sonarr; } #couchpotato location ^~ /couch { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:5050/couch; } #transmission location ^~ /transmission { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:9091/transmission; } #sabnzbd location ^~ /sabnzbd { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass https://192.168.1.100:9090/sabnzbd; } #plexpy location ^~ /plexpy { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:8181/plexpy; proxy_bind $server_addr; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Ssl on; } #rutorrent location ^~ /rutorrent { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:82/; } #ombi - non-restricted access location ^~ /ombi { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:86/ombi; } #pi-hole location ^~ /pihole { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.4/admin/; } } TODO any help would be appreciated: Figure out how to host the wordpress site on port 443 https on its unique domain, without breaking everything else currently running in the 443 server block on their seperate duckdns.org domain

Same with me, i cant manually add torrents anymore, also couchpotato and sonar cant add torrents either.... seems to be after the last update, I haven't changed anything else

I GOT IT WORKING!!! I forked a different terraria docker, tinker tinker a bit... But it works! Add this repo to your docker template repositories https://github.com/mulletboy/docker-template Then add the container from the option that will appear in your template list, configure it like my screenshot Once the it builds successfully, give it another 5 minutes to generate the world Then join using your terraria client at [unraidserverip]:7777 For some reason its laggy as hell and plays in slow motion until you turn frame skipping on in the video settings menu, but then it plays fine *note* i have absolutely no idea what I am doing and I probably did everything wrong, I forked another terraria docker which worked but was way out of date and tinkered with it, created a docker xml thing and tinkered with it some more, created a hub.docker.com account (im not sure what this is for... but i noticed everyone else had one so i did it too) somehow got them linked and did *stuff* eventually it built successfully and after that it loaded in Unraid properly If someone wants to tell me how to make this better, fix any issues, and generally setup a docker template properly please give me simple instructions

I have been messing around with getting a Terraria server running as a docker in unraid So far I have found the closest to being successful i have been is this docker https://hub.docker.com/r/sixarm/terraria/ Add that using community apps, set a path for it to save stuff in your appdata folder, and wait a minute or two for it to generate the world on my pc i join at [unraidserverip]:7777 it will briefly run then it crashes with some exception that is beyond me... if anyone who knows what they are doing could look into this and see if its an easy fix to get it working, would be so awesome!

Thats what I thought too updating to 6.2 is what prompted me to give this docker another go however it still didnt work until I tried the above

I was having this exact issue still however your solution of mapping app data direct to a disk e.g. /mnt/disk1/appdata/unifi instead of /user/ did work for me... I would add however that simply remapping the user share and restarting the docker didnt fix it, I had to fully delete the docker image AND delete all traces of the old /appdata/unifi folders from my /user/ share, then reinstall it mapped to /disk1/ before it would work

Updated mostly fine and all my things are currently live and working however I have noticed that all my docker apps have the update ready message next to them... but every one of them results in an error "layers from manifest don't match image configuration" when i attempt to update

I want to use ruTorrent to create torrent files based on files I have moved out of the downloads directory and into another share location As such i have exposed more directories as per screenshot below However in ruTorrent when navigating to any location other than the /downloads/... it errors "Incorrect directory ()" It is like it is hardcoded to only allow me to access the folder mapped to /downloads/ Any ideas?

I got it working My problem was that I was an idiot.... i was entering a username and password when i had not configured a username and password in ruTorrent duuuur herp durp For anyone else's reference host: IP of unraid server (192.168.1.100 for me) port: 8080 is default, (i remapped mine to 82) urlpath: RPC2 category: TV everything else default

Has anyone got this Sonar working with Linuxserver.io's ruTorrent docker? http://lime-technology.com/forum/index.php?topic=47299.0 I for the life of me cant figure out what config is required on this screen to make it work? If someone could post a screenshot of their working Sonar config for ruTorrent i would really appreciate it

Stop --> Start did not update it for me I had to Stop --> Edit --> Save Triggered a rebuild and downloaded the updated version Then it was updated to 0.10.5 fine

Mulletboy, you don't need to change anything in rtorrent add this to your Apache default.conf RewriteRule ^/rtorrent$ /rtorrent/ [R] <Location /rtorrent> ProxyPass http://192.168.0.100:82/ ProxyPassReverse http://192.168.0.100:82/ </Location> This worked perfectly for me! (once i found my typo in the IP address lol) Thanks

How do I change the URL Base for RUTorrent? Currently I access the webgui through http://192.168.1.100:82/ I need to be able to access it from http://192.168.1.100:82/rutorrent/ I have already done this for sonar, couchpotato, plexpy, transmission and other things... but cant for the life of me find out how to do it for the RUTorrents webgui... This is so I can easily configure it with reverse proxy under apache and then have it exposed through muximux My apache sites config currently has the following settings

So I kinda threw in the towel here... I installed the Unifi docker from pducharme's repository, same settings as i had before (remap all ports to 7xxx) from the originals and same appdata config location It "just worked"... straight away, no errors in the logs, web gui came straight up from the url given by the app icon... I would still be keen to get Linuxserver.io's docker working, because i am currently using 8 of their other dockers perfectly and now this is the only docker i use that itsn't one of theirs... But for now I am up and running and managing my Unifi AP's no problems

Aaaand no dice Delete the docker image and container, deleted the unifi appdata folder and config, reinstalled from scratch exact same result. docker webgui loads page cannot be displayed log files full of the same errors as above... here 3 screenshots of my setup... does this help? can anyone see anything wrong with my setup?

Yeah I can see the docker build works fine.... but I can see in the Unifi server logs (the first logs i posted) that the app is crashing unfortunately I am not very good at interpreting this... the stack trace keeps repeating and it keeps trying to restart.... if i leave the docker running the log files get pretty big... I will totally delete and re-add the docker like you suggest and report back

I did a force update to simulate re-installing (am i right to do that?) Results quoted below The 8080 port is already in use (sabnzb) so i changed the port to 7080 for unifi

Hey I am having trouble getting this docker working, cant access the webui and the Unifi logs are quoted below, can anyone help me?