SRTG

I'm trying to set up my first Authelia end point and also get this error. Has anyone found a solution to this ? I'm effectively in a log in loop with a 401 error... time="2023-08-05T20:03:17+01:00" level=debug msg="Successful 1FA authentication attempt made by user 'USER'" method=POST path=/api/firstfactor remote_ip=myIP time="2023-08-05T20:03:17+01:00" level=debug msg="Required level for the URL https://mydomain/ is 1" method=POST path=/api/firstfactor remote_ip=myIP time="2023-08-05T20:03:17+01:00" level=debug msg="Redirection URL https://mydomain/ is safe" method=POST path=/api/firstfactor remote_ip=myIP time="2023-08-05T20:03:18+01:00" level=debug msg="Check authorization of subject username= groups= ip=IP and object https://mydomain/ (method )." time="2023-08-05T20:03:18+01:00" level=info msg="Access to https://mydomain/ (method unknown) is not authorized to user <anonymous>, responding with status code 401" method=GET path=/api/verify remote_ip=IP

🥴 ah no Thanks for confirming I'll just have to make do until I upgrade my board and CPU !

@Hoopster Interesting, I've added this setting. I have an i5-4590 so maybe the fact it's an older QSV processor is an issue in itself ! What I've tried so far: -Added "/dev/dri" as a device in handbrake -Go file modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 -Tried "--device=/dev/dri/card0:/dev/dri/card0 --device=/dev/dri/renderD128:/dev/dri/renderD128" in extra parameters -Added blank config file to whitelist the driver "touch /boot/config/modprobe.d/i915.conf" -Added "i915.alpha_support=1" to syslinux boot Right now I can encode a 2-hour bluray in around 2hrs 15 mins but only in H264 (h265 is at least double this). Not the end of the world but CPU utilisation is a solid 100%. QSV should cut the time down and give me some headroom! I will try handbrake forums and post a solution if I ever find one.

Yes, in terminal I see card0, render D128. I'm running UNRAID 6.11.5. I did notice something in handbrake_activity_logs.txt. It seems to confirm QSV is available but it can't locate the driver ? I'm a little confused on how Plex can see this but Handbrake can't. So a possible solution is terminal: touch /boot/config/modprobe.d/i915.conf ? Thanks for your help so far!

The QSV options don't appear in the dropdown. Mine still look like this: I've already added /dev/dri device as below but still no luck.

I'd like to bump this. I have the same issue as @Alvin Leong except I'm using Plex. HW transcoding works fine but I can't seem to enable quicksync on handbrake. I've added /dev/dri as a handbrake device parameter so if Quicksync works in Plex it should show up here. I added the below to the "go file" but no joy. modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri If anyone could provide a steer it would be much appreciated!

Ok so have moved UNRAID to 5000/5001 and NPM is now on 80/443. Think I'm making progress but not there yet. -NPM is now host network with server IP and when I go to http://mypublic IP I get the NGINX congratulations screen, which is what I want !? -added new proxyhost and am able to get a cert from let's encrypt (couldn't before) -Now, when I click the proxyhost link to my domain I get "400 bad request The plain HTTP request was sent to HTTPS port nginx" Is this a config problem on the cloudflare side ? EDIT: simply changing the proxyhost to https from http it works. I think nextcloud needs https (although not sure why yet). Thank you very much mgutt for your help. I'm off to do some cartwheels 😆

Landing on unraid log would mean port 80 is not being forwarded to 8080 ? I guess, public IP takes me to http://server:80. I have disabled port forwards for now but any idea why this is happening - am I missing an obvious config edit somewhere forcing use of port 80? Container was on a custom network with nextcloud but at the moment it's on bridge as I try different configs. I've had the 404 error on all network variations. Thanks for your help

I changed this back to http and get the same error unfortunately

Hello, What is going wrong with my configuration ? -server is 192.168.0.2 -nextcloud is on port 444 -cloudflare A record points to my public IP -cloudflare set to "full" on SSL/TLS, records are "proxied" -port forwarded as follows on a sky router (inbound) -nginx settings (ports are 4443, 8080) Result is a 404 not found error when accessing externally ! -I can access nextcloud locally on 192.168.0.2:444 -Tried this from NGINX terminal: /tmp # curl -sS http://192.168.0.2:444 >/dev/null && echo "Container is reachable" Container is reachable -Tried host, custom br0 and bridge networks Tried- http://<mypublicIP> which lands on the UNRAD log in screen so is this a port issue ? I've opened and directed 80 & 443 as above so I'm stumped as to why it's not redirecting to NGINX.

Accessing external IP on https shows the same message - "404 not found ". I should have said the not found has a "nginx" footer so it's the same message. Changing to http I hit the log in page for the server. The page does have the correct nextcloud address and is secure with uploaded certs but just doesn't seem to be finding nextcloud on the server. Tried this from NGINX terminal: /tmp # curl -sS http://192.168.0.2:444 >/dev/null && echo "Container is reachable" Container is reachable

Hi, looking for some assistance setting this up with nextcloud. I've been messing around for longer than is healthy and hit a wall! I have a domain on cloudflare with nextcloud CNAME - nextcloud.mydomain.com. I configured NGINX to point to nextcloud but get a 404 error. I can access nextcloud locally when I remove the "overwrite" commands in the config. -nextcloud, cloudflare ddns & nginx all on custom network (proxynet) -server is 192.168.0.2 nextcloud is on port 444 -port forwarded as follows on a sky router -cloudflare A record points to my public IP -nextcloud config attached -nginx settings -cloudflare set to "full" on SSL/TLS, records are "proxied" Result is a 404 not found error when accessing externally ! nextcloud.config.edit.txt

@luisalrp My issue was incorrect server addresses and port mappings across the Arr apps. I just didn't have an understanding of what to use for these but since figuring it out all are working perfectly. The Prowlarr, Radarr and Sonarr proxy address should be your server address - as below My next issue was using host addresses instead of app addresses when linking prowlarr to other Arr apps. These should be http://app address:port map i.e. when on unraid docker screen port mappings are listed "app to host" left to right. Use the app address on the left hand side of this list not the host address on the right when linking apps. Use the same app address when linking deluge in Arr apps. The "Host" field should have the app address only, no http.

I managed to get around this by disabling flaresolverr and using deluge proxy instead. I can now add indexers which return searches in prowlarr. These also show up in radarr as linked indexers "(prowlarr)". The problem now is I have lost connection to Deluge in both apps with the same download client configuration settings as before. Is there an additional setting I need to add when using Deluge proxy ? Pulling my hair out at this stage! My proxy settings in prowlarr - http(s), local server address, port 8118, bypass proxy for local addresses ticked. Log states as follows:

I have an issue connecting indexers to Prowlarr and am a bit stumped. Newby here with a one week old server out of my depth but I will try explain. I have prowlarr set up using flaresolverr as a proxy, which tests fine, but I get errors when testing any indexer connection. If I disable RSS then re-enable the indexers appear to work (green tick) but when I actually search in Prowlarr, the logs produce this and I go back to failure: Radarr also shows this: Frustratingly close to getting this working after much tinkering so appreciate a steer from anyone.