December 18, 2025Dec 18 Weeks and hours I have spent trying to get self-signed certificates to work. Finally had it working except my browser's did not recognize Cert as from a CA authority. (Thought I imported everything needed).Giving up, and will go with the easiest way to get this done. I don't want to expose my Unraid to the Internet, but looks like I have no choice.I even tried UnRaid's SSL: Yes and Local: TLD Local and Provisioning. The links that are generated all give me the browser warnings. (Which I understand I should not).If I click on https://192.168.xx.xxx/ I get a browser warning.If I click on https://UnRaid.local/ I get a browser warning.If I click on https://192-168.xx-xxx.3855c481cd2ee31f586ef3f634076199d1b49eae.myunraid.net/ , I get a browser warning.Help, what's the best way to get there and put this SSL stuff to rest. Simplest and ideally not opening anything to the Internet.
December 18, 2025Dec 18 Community Expert Take a look at this video: https://www.youtube.com/watch?v=OTK4OwpxFek
December 18, 2025Dec 18 Author Following the video carefully and enabled provisioning, unlike the instructor, I get an error when clicking on the provided long URL. (I have tried this previously with an error as well).I get a similar error with Chrome.The provisioned link does not work.I used the provided url: https://192-168-60-235.2855c481cd2ee31f586ef3f634076199d1b48eae.myunraid.net/ Edited December 18, 2025Dec 18 by RaidPC Added specific url
December 18, 2025Dec 18 Community Expert 18 minutes ago, RaidPC said:The provisioned link does not work.That suggests to me your router is not correctly configured to port forward the HTTPS port.
December 18, 2025Dec 18 Community Expert Be sure that you have read the help for setting the usage of SSL/TLS. There are a few gotcha's....
December 18, 2025Dec 18 Author I went into my router, dd-wrt, and set Port Forwarding: set my Unraid at "Protocal TCP" and" Port From 80" with the "IP address" of the Unraid Server "to Port 443."Same error when I click on the fore-mentioned long link. As screen capture. We can't connect to the server at .....
December 19, 2025Dec 19 Community Expert It's not port 80 that you need to forward:https://docs.unraid.net/unraid-connect/remote-access/#initial-setup
January 2Jan 2 Author I checked one docker, Nextcloud, that by default wanted to use port 443; but I had changed it to Host Port 4743 during the setup and that is the port I use when accessing it. I have Pi-hole forwarding Unraid to Nginx and the DNS part works fine with its DNS name. I run into problems when I try to tie it down to HTTPS. I think I need to take the unraid_bundle.pem file that resides in the boot thumb drive into Nginx and add it under certificates, but the latter does not recognize that extension.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.