-
Posts
810 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by casperse
-
-
1 hour ago, mgutt said:
If a container runs in the host network it uses it's default ports. This is a usual behavior of all containers.
Did you accidentally change both ports, internal and external? This is not visible in the screenshot. Only if you edit the entry. Finally it would be interesting to see what it looks like after the container has been started.
No I only changed the ports like before not the container ports
I started the docker:
Opening the settings I can see:
Opening the EDIT HTTPS:
The container ports are changed to the same port as my Host port?
And only way to get it back is doing a re-install
This is so strange, it happens when I change Host ports or I change network between Host & custom net Prox
net? - can it be somekind of bug? (I have refreshed the webpage and the values are not cached)
-
Hi
When I cahnge ports the container act funny
But inside it looks okay:
So far the only way to fix the port this have been to remove the container and install it again?
If I change the proxynet to host :
How can it change the ports...
I can access the UI but the proxi stopped working after the port change (And yes the ports are open)
Also disabled any 443 redirect to unraid disabling the "My server" remote access feature
I love the docker and the UI but it dosent seem as stable as Swag?
-
On 7/2/2021 at 12:17 AM, mgutt said:
This is the only reliable way to use NPM through IPv6:
1.) Change Unraid's HTTP and HTTPS ports to 5000 and 5001:
2.) Install NPM by using the host network:
3.) Open the ports 80 and 443 in your router:
4.) Open the NPM WebGUI and after changing the login, you can add a proxy host (see next post for Plex as an example).
5.) If you only want to type "tower" in your browser to reach your Unraid WebGUI, add this Redirection Host in NPM:
Further explanation:
IPv6 does not need port forwarding and many routers don't support it. So it's often not possible to forward internet traffic from port 443 (http) to a custom port like 8443. By that we have two options: Run NPM in the br0/custom network with a fixed ip address or run it in the host network (bridge has IPv6 disabled). I tried everything, but br0/custom isn't reliable as its not possible to define a fixed IPv6 without passing the IPv6 prefix and if your provider assigns a new IPv6 prefix, the container is offline and stays offline until we manually change the containers IPv6. And changing the IPv6 alone does not work as the "old" IPv4/IPv6 combination is internally reserved from the docker service. So its not only needed to change the IPv6 of the container, we additionally need to restart to entire Docker service itself.
I just installed the NMP Official (Had the old docker) and set everything up like you wrote
Except the 5000/5001 (Synology ports) so I changed it to 6000/6001
But now the Unraid comes with the "My Servers" plugin and when this is running and I try to do the:
(I use 6000 and my own server name ;-))
I can not access the UNRAID UI anymore......
So is there any workaround for having this setup with the "My Server" plugin
Remote access from this requires you to let Unraid get a cert. and run HTTPS
Br
Casperse
-
Hi @manbearwiz
I am trying to get the youtube-dl-server working with a proxi
I found the conf option where you could set this
But I am not sure how to get the conf working on the docker?
https://github.com/ytdl-org/youtube-dl/blob/master/README.md#configuration
-
-
I am now finally moving from SWAG to NPM
But some of the more difficult ones I cant get working
youtube-dl-server
This docker have a url path that goes like this:
http://192.168.0.6:8282/youtube-dl
SWAG worked by doing this:
# make sure that your dns has a cname set for youtube-dl-server and that your youtube-dl-server container is named youtube-dl-server server { listen 443 ssl; listen [::]:443 ssl; server_name youtube.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app youtube-dl-server; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; } location ~ (/youtube-dl/)?/socket { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app youtube-dl-server; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port/youtube-dl; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; } }
Can someone point me in the right direction 🙂
-
Does anyone have a rsync script example? they would like to share?
I am strugeling to create a script to initiate a rsync to my Unraid server from an external media server
Sofar I have managed to use dockers like Resilio sync but they ar not cutting it anymore
Or would I need to initiate this from the remotes server to my Unraid server as the target server?
Sofar I have been reading up on what I could fine, but the post is very old...
-
On 9/28/2021 at 2:05 PM, dlandon said:
Provide a full screen shot and post your diagnostics.
Sorry did a reboot and then everything was okay again, so some caching of the old drive was somehow still shown by UAD
-
After renaming and unmount and mounting again I get this:
rsync dosent copy partitions, so somehow UAD is caching the old mounted drive with the same name
and showing 12.0TB on a new 18TB drive
Anyway to fix this? stop and start UAD services?
-
21 minutes ago, JorgeB said:
You should post in the UD plugin support thread, rsync doesn't touch the partitions.
Great then I didn't screw up! - 🙂 Thanks for confirming this I am new to using rsync
-
On 9/26/2021 at 7:08 PM, casperse said:
Have enyone got this Unraid plugin working? - I seem to have permissions problems after a encode
-
Hi All
I am replacing a 12TB Unassigned drive with a new 18TB and I did a:
rsync -avPX /mnt/disks/SEED/ /mnt/disks/SEED_NEW/
and later a update:
rsync -auPv /mnt/disks/SEED/ /mnt/disks/SEED_NEW/
But after unmounting the drives and renaming it to the "old name" replacing my old UAD drive I keep getting this:
After remounting the drive I no longer have luks (encryption) and also it shows the drive as 12TB partition under the 18TB drive
Is my rsynch command wrong?
is it UAD that somehow just cashes the old drive (I havent re-booted - to many things running so I cant right now)
-
So I found a Unraid plugin in the stack for permissions
But when I add it I get error:
Pre-processing - Set file permissions for UnRaid Plugin error! Error: Command failed: chown nobody:users
I remember in the docker resilio-sync you could do a:
Any input on how to get this working?
Thanks!
-
2 hours ago, dlandon said:
cat /proc/mounts
rootfs / rootfs rw,size=32739196k,nr_inodes=8184799 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 devtmpfs /dev devtmpfs rw,relatime,size=32739204k,nr_inodes=8184801,mode=755 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /dev/shm tmpfs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 cgroup_root /sys/fs/cgroup tmpfs rw,relatime,size=8192k,mode=755 0 0 cpuset /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0 cpu /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0 cpuacct /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 blkio /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0 memory /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0 devices /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0 freezer /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0 net_cls /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls 0 0 perf_event /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0 net_prio /sys/fs/cgroup/net_prio cgroup rw,relatime,net_prio 0 0 hugetlb /sys/fs/cgroup/hugetlb cgroup rw,relatime,hugetlb 0 0 pids /sys/fs/cgroup/pids cgroup rw,relatime,pids 0 0 tmpfs /var/log tmpfs rw,relatime,size=131072k,mode=755 0 0 /dev/sda1 /boot vfat rw,noatime,nodiratime,fmask=0177,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,flush,errors=remount-ro 0 0 /dev/loop0 /lib/modules squashfs ro,relatime 0 0 /dev/loop1 /lib/firmware squashfs ro,relatime 0 0 hugetlbfs /hugetlbfs hugetlbfs rw,relatime,pagesize=2M 0 0 overlay /lib/modules overlay rw,relatime,lowerdir=/lib/modules,upperdir=/var/local/overlay/lib/modules,workdir=/var/local/overlay-work/lib/modules 0 0 overlay /lib/firmware overlay rw,relatime,lowerdir=/lib/firmware,upperdir=/var/local/overlay/lib/firmware,workdir=/var/local/overlay-work/lib/firmware 0 0 rootfs /mnt rootfs rw,size=32739196k,nr_inodes=8184799 0 0 tmpfs /mnt/disks tmpfs rw,relatime,size=1024k 0 0 tmpfs /mnt/remotes tmpfs rw,relatime,size=1024k 0 0 nfsd /proc/fs/nfs nfsd rw,relatime 0 0 nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 tmpfs /tmp/EmbyRamScratch tmpfs rw,relatime,size=8388608k 0 0 tmpfs /tmp/PlexRamScratch tmpfs rw,relatime,size=8388608k 0 0 tmpfs /tmp/EmbyRamScratch tmpfs rw,relatime,size=8388608k 0 0 tmpfs /tmp/PlexRamScratch tmpfs rw,relatime,size=8388608k 0 0 /dev/mapper/md1 /mnt/disk1 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md2 /mnt/disk2 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md3 /mnt/disk3 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md4 /mnt/disk4 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md5 /mnt/disk5 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md6 /mnt/disk6 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md7 /mnt/disk7 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md8 /mnt/disk8 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md9 /mnt/disk9 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md10 /mnt/disk10 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md11 /mnt/disk11 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md12 /mnt/disk12 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md13 /mnt/disk13 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md14 /mnt/disk14 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md15 /mnt/disk15 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md17 /mnt/disk17 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md18 /mnt/disk18 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md19 /mnt/disk19 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md20 /mnt/disk20 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md21 /mnt/disk21 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/md22 /mnt/disk22 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/nvme0n1p1 /mnt/cache btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0 shfs /mnt/user0 fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0 shfs /mnt/user fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0 tmpfs /tmp/EmbyRamScratch tmpfs rw,relatime,size=8388608k 0 0 tmpfs /tmp/PlexRamScratch tmpfs rw,relatime,size=8388608k 0 0 /dev/loop2 /var/lib/docker btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0 /dev/loop2 /var/lib/docker/btrfs btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0 /dev/loop3 /etc/libvirt btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0 nsfs /var/run/docker/netns/default nsfs rw 0 0 nsfs /var/run/docker/netns/af0ca5d48ca0 nsfs rw 0 0 nsfs /var/run/docker/netns/c69b5061ae08 nsfs rw 0 0 nsfs /var/run/docker/netns/a2eec510e8c2 nsfs rw 0 0 nsfs /var/run/docker/netns/6d7e60f58521 nsfs rw 0 0 nsfs /var/run/docker/netns/2f86374148d1 nsfs rw 0 0 nsfs /var/run/docker/netns/08afabb265ec nsfs rw 0 0 nsfs /var/run/docker/netns/e56b4af7f70b nsfs rw 0 0 nsfs /var/run/docker/netns/c6f9f26bc3bc nsfs rw 0 0 nsfs /var/run/docker/netns/bea51fff217e nsfs rw 0 0 nsfs /var/run/docker/netns/d331e0d43b95 nsfs rw 0 0 nsfs /var/run/docker/netns/fcc5d03ff157 nsfs rw 0 0 nsfs /var/run/docker/netns/4942e60e1f4d nsfs rw 0 0 nsfs /var/run/docker/netns/80bd94893048 nsfs rw 0 0 nsfs /var/run/docker/netns/c2d0c3ca95d4 nsfs rw 0 0 nsfs /var/run/docker/netns/0ed243b5f45c nsfs rw 0 0 nsfs /var/run/docker/netns/a4af87ec6a28 nsfs rw 0 0 nsfs /var/run/docker/netns/a43c3a83de47 nsfs rw 0 0 /dev/mapper/SEED /mnt/disks/SEED xfs rw,noatime,nodiratime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 /dev/mapper/SEED_NEW /mnt/disks/SEED_NEW xfs rw,noatime,nodiratime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0 nsfs /var/run/docker/netns/5da03b4a5235 nsfs rw 0 0 nsfs /var/run/docker/netns/f27c01f97146 nsfs rw 0 0 nsfs /var/run/docker/netns/0596f205e063 nsfs rw 0 0 nsfs /var/run/docker/netns/f5960a6c3a6b nsfs rw 0 0 nsfs /var/run/docker/netns/78640e0fa51f nsfs rw 0 0 nsfs /var/run/docker/netns/dec306ebfaa4 nsfs rw 0 0 nsfs /var/run/docker/netns/2058a66d1423 nsfs rw 0 0
-
21 hours ago, dlandon said:
I don't get that. It normally shows xfs. Can you post your diagnostics so I can have a look?
Sure thing! - The mount and drive works perfectly so this is just a UI thing 🙂
-
17 minutes ago, dlandon said:
An encrypted disk will show 'luks' until it is mounted, then it will show the file system. In your case 'xfs'.
Thanks - And the double xfs,xfs is beacuse it list the partition below?
-
21 minutes ago, casperse said:
Hi Big fan!
I just added a new UAD drive that I wanted to replace with a new bigger drive
Adding and mounting the drive was no problem
I then ran the:
rsync -avPX /mnt/disks/SEED/ /mnt/disks/SEED18
Also did a update of any new files:
rsync -auv /mnt/disks/SEED/ /mnt/disks/SEED18
I then renamed the new drive to the old drive name and stopped and started the Array
And now it looks like I have a partition on the new drive in the size of the old one?
But it looked okay before the restart?
Also why does the FS for the format says "luks" ? before reboot it was "xfs,xfs"
Removed the partition on the new drive and formattet id with XFS encrupt. did a reboote and now have the old drive with xfs, xfs again?
-
Hi Big fan!
I just added a new UAD drive that I wanted to replace with a new bigger drive
Adding and mounting the drive was no problem
I then ran the:
rsync -avPX /mnt/disks/SEED/ /mnt/disks/SEED18
Also did a update of any new files:
rsync -auv /mnt/disks/SEED/ /mnt/disks/SEED18
QuoteUpdate: Did I miss a "/" on the old drive? did I copy the partition?
I then renamed the new drive to the old drive name and stopped and started the Array
And now it looks like I have a partition on the new drive in the size of the old one?
But it looked okay before the restart?
Also why does the FS for the format says "luks" ? before reboot it was "xfs,xfs"
-
Happy to hear you found a solution! 🙂
No answers normally means that no one knows the answer to your question😞
You are using Unraid as a baremetal for running a Synology NAS with 5 passthrough drives.
My setup is much simpler just a small partition for the Synology apps 100G
And a VM disc for some photo data that I can mirror to the Unraid drives as a backup
So I can restore easily when a upgrade fails (Using the VM backup app)
-
Hi Everyone
I have for a very long time used my Quadro P2000 for my dockers (Shared between encoder needs) using passthrough and it works perfectly!
But my CPU have a iGP but never managed to get it working with my VM's (Intel® Xeon® E-2176G CPU @ 3.70GHz)
I have now read about allot of updates and I can see plugin support making it easier to see all IO and HW specs on Unraid
What I am asking is there any "Easy" way to get the iGPU up in the list of passthrough HW on the VM configuration UI webpage?
My usage would be to use the iGPU on a VM running adobe for some light video editing
My Go file:
Do I need to remove the above lines for the iGPU in the GO file now?
Dont think I need to add anything to the global conf file?
Again I did try to get this working some time ago (Years) but with all the improvements to Unraid it might work now?
(Runing the latest and greatest version 6.9.2
Cheers and thanks for all your valuable input and this great forum
-
Update I tried this:
server { listen 443 ssl; listen [::]:443 ssl; server_name maindomain.dk; include /config/nginx/ssl.conf; # add_header X-Frame-Options "SAMEORIGIN" always; add_header Strict-Transport-Security "max-age=15768000; includeSubDomians; preload;"; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } # Make a regex exception for `/.well-known` so that clients can still # access it despite the existence of the regex rule location ^~ /.well-known { location = /.well-known/carddav { return 301 /remote.php/dav/; } location = /.well-known/caldav { return 301 /remote.php/dav/; } # Anything else is dynamically handled by Nextcloud location ^~ /.well-known { return 301 /index.php$uri; } try_files $uri $uri/ =404; } }
And I got it reduced to this last one:
To anyone finding this "webfinger" error
Last error is related to cache (In chrome do the following) Open Dev Tools (F12), and while this is open right click on "normal" refresh button on your top left and select Empty cache and hard reload.
And all us ok
-
Configuration change needed after latest Nextcloud update to Nextcloud 21.0.1
Error message:
My existing configuration in Swag:
server { listen 443 ssl; listen [::]:443 ssl; server_name maindomain.dk; include /config/nginx/ssl.conf; # add_header X-Frame-Options "SAMEORIGIN" always; add_header Strict-Transport-Security "max-age=15768000; includeSubDomians; preload;"; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } }
I have found different solution on the net that I cant "translate" into my SWAG configuration file
QuoteTo be more precise, I have added the following lines to my nginx config file:
location = /.well-known/webfinger { rewrite ^/.well-known/webfinger /public.php?service=webfinger last; } location = /.well-known/nodeinfo { rewrite ^/.well-known/nodeinfo /public.php?service=nodeinfo last; }
Or this one:
location ^~ /.well-known { location = /.well-known/carddav { return 301 /remote.php/dav/; } location = /.well-known/caldav { return 301 /remote.php/dav/; } # Anything else is dynamically handled by Nextcloud location ^~ /.well-known { return 301 /index.php$uri; } try_files $uri $uri/ =404; }
If anyone have this working then it would be great if you could share your configuration file
-
Hi All
I hope someone can help me out?
I have successfully had this running with Sonarr & Radarr but now I am moving it to another where the download path is different
Is it possible to change the default /Data to /downloads/ looking at Sabnzd I can see that it says:
And it would be easy to just change it in the Docker:
The reason I would like to change it is that I have a working setup "Remote Path Mappings"
So I need for all download clients to look in the same defined path
Hope this makes sence to some that might have the same setup?
-
On 3/17/2021 at 5:36 PM, C-Fu said:
This is not the XML its the HW passthrough of the eth. - I didnt do any manuel editing I just crossed [X] of the 4 LAN in the UI (Nothing virtual, MAC etc clean passthrough of the HW)
Space invader makes a great video on how to get this working
(Sorry whole family have ben down with Corona so that's why I haven't replied before now 🙂)
- 1
Unraid UI port change not working?
in General Support
Posted · Edited by casperse
Hi All
I am trying to change my Unraid port setting from 80 & 443 to 6000 & 6001
After changing the ports in the UI....
It was NOT possible to access the Unraid GUI anymore?
Not by IP or hostname?
It tried to connect by IP:PORT and also I could see Unraid trying to access: http://hostname.local:6000/
(By the way is the hostname case sensitive?)
So I did a telnet and I had to edit the ident.cfg file in \\flash\config back to
# Generated settings: NAME="SERVERNAME" timeZone="Europe/Paris" COMMENT="The Ultimate Media Server" SECURITY="user" WORKGROUP="WORKGROUP" DOMAIN="" DOMAIN_SHORT="" hideDotFiles="no" localMaster="yes" enableFruit="no" USE_NETBIOS="yes" USE_WSD="yes" WSD_OPT="" USE_NTP="yes" NTP_SERVER1="time1.google.com" NTP_SERVER2="time2.google.com" NTP_SERVER3="time3.google.com" NTP_SERVER4="time4.google.com" DOMAIN_LOGIN="Administrator" DOMAIN_PASSWD="" SYS_MODEL="Xeon E-2100G based 24-bay NAS system" SYS_ARRAY_SLOTS="24" USE_SSL="no" PORT="80" PORTSSL="443" LOCAL_TLD="local" BIND_MGT="no" USE_TELNET="yes" PORTTELNET="23" USE_SSH="yes" PORTSSH="22" USE_UPNP="no" START_PAGE="Main"
Then a restart: /etc/rc.d/rc.nginx restart
Also when trying to start with SLL/TLS set to Auto I got this error:
root@SERVER:/boot/config# /etc/rc.d/rc.nginx restart Checking configuration for correct syntax and then trying to open files referenced in configuration... nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful Shutdown Nginx gracefully... Stopping unraid-api process... Process stopped! Starting Nginx server daemon... nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/etc/ssl/certs/unraid_bundle.pem" root@SERVER:/boot/config#
After this I could login but looking at the UI I still se the 6000/6001 ports? (See below)
HTTPS is grayed out?
How do I get this working with port 6000/6001 ?
I need port 80 & 443 to get my nginx-proxy-manager-npm-official working with IPv6
see more about this here: