• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by ljm42

  1. Woohoo! Glad this is confirmed to work. FYI to anyone else trying this - Fix Common Problems doesn't know that we support this type of cert yet so it will complain that the cert has an invalid url. Please ignore that, I need to update FCP
  2. Please connect via SSH and type "use_ssl no", then you will be able to access the server via http. It will tell you the specific url. If you get an error when logging in, please clear your browser cache. Then grab the diagnostics.zip file (from Tools -> Diagnostics) and upload it here
  3. I'm sorry, but I really don't see any why you would not be able to login using either of these urls: http://Tower.local:85 in Unraid 6.10.1 if those same urls work in 6.9.2. Thank you for testing multiple systems in incognito mode. The next release has a change that will potentially help people who are using the default ports of 80/443. But you don't need that change because you are using non-standard ports. At the moment I am somewhat stumped.
  4. Hi @Joedy, I dug into it a bit and realized that because of the improvements to SSL handling in Unraid 6.10 we can actually support the Subject Alternative Names in certificates now, and handle them properly. If you are ok testing a pre-release version of Unraid, 6.10.2-rc2 is available by going to Tools -> Update OS and choosing the "next" branch. It would be great if you could test and confirm that your wildcard cert works now. You would also need these settings: - Your Server name (on Settings -> Identification) should be "backup" - Your Local TLD (on Settings -> Management Access) should be "horts.com.au" This will make the url to the server: https://backup.horts.com.au If you aren't comfortable doing that, would you please send me a DM with your certificate file? Then I'll confirm it is being parsed correctly. Note: BEFORE sending the .pem file, open it in a text editor and remove everything between these lines: -----BEGIN PRIVATE KEY----- -----END PRIVATE KEY----- That private key needs to stay on your servers, do not send it to anybody
  5. Please post a screenshot of the message. If this is Unraid 6.10 I have a feeling it is asking you to SET a root password, not provide one.
  6. matches your diagnostics, good. So if you try to access, what happens? It should redirect you to: https://hash.unraid.net so you can login. If that fails, what exactly happens? Are there any error messages?
  7. Hi folks, would you please update to the latest plugin and let me know if it solves your connection issues? https://forums.unraid.net/topic/112073-my-servers-releases/#comment-1130790
  8. Hey everyone, we've released My Servers plugin version 2022.05.24.1752, go to the Plugins tab and check for updates! ## 2022.05.24 ### This version resolves: - Some systems always offline or "Unable to connect to mothership" - Removed GUIDs from `unraid-api report -v`, this output can be posted to the forums now - Resolved some "Unraid.net re-authentication required" messages - Resolved some "unexpected response for owner" messages ### This version adds: - Significant reduction in the frequency of data being sent from unraid-api to mothership. Now most data is sent only when you are actually viewing the My Servers dashboard ( https://forums.unraid.net/my-servers/ ). BTW if you are curious about the data being sent, see https://wiki.unraid.net/My_Servers#Privacy
  9. Thanks, I've updated the docs. Basically, if the certificate is provisioned in 6.10 it will use the myunraid.net domain, if it was provisioned in an earlier version of Unraid it will use the unraid.net domain.
  10. Please see https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down I've locked this historical thread, if you have follow-up questions please ask in the My Servers sub-forum, thanks! https://forums.unraid.net/forum/94-my-servers-plugin-support/
  11. I am sorry that you are unable to use your existing wildcard certificate. It should not have worked under 6.9.2 either, if it did it was an accident. One of the major focuses of Unraid 6.10 is security, as such we are being very strict about certificates and ensuring the server only responds to specific urls. You might consider getting a certificate specifically for "backup.horts.com.au"
  12. To use this url: https://backup.horts.com.au Your Server name (on Settings -> Identification) should be "backup" Your Local TLD (on Settings -> Management Access) should be "horts.com.au" When you change "Use SSL/TLS" to Yes, Unraid will automatically make a self-signed certificate with the "Subject" of "backup.horts.com.au" and place it on the flash drive here: config/ssl/certs/backup_unraid_bundle.pem The screenshot you provided of your custom certificate uses the "Subject Alternative Name" field, which Unraid ignores. It sort of worked in 6.9.2, but only by accident. It will not work in Unraid 6.10. If you want to provide your own certificate, you need to make sure the "Subject" of the certificate is either "backup.horts.com.au" or "*.horts.com.au". Then overwrite the certificate that Unraid created on your flash drive: config/ssl/certs/backup_unraid_bundle.pem You can then change "Use SSL/TLS" back to No and then to Yes again to get it to see the cert. Or you can open a web terminal and run: /etc/rc.d/rc.nginx reload Note that if the "Subject" of the cert is not correct, the certificate will be deleted and replaced with a self-signed cert that has the correct Subject.
  13. You showed a screenshot of your browser where it showed you the certificate information. Click the Details tab and find the "Subject" field. What url is listed there in the "Subject" field? A screenshot of this would be great. What url do you want to use to access the server?
  14. It looks like you Provisioned a myunraid.net cert. That is fine, in 6.10 you can use your own custom cert as well. The Settings -> Management Access page does not show details about personal certs but they do work fine. You have to make sure to set the Server Name and Local TLD of the server to match the Subject of the certificate. Wildcards are supported too. Full instructions are in the manual: https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29 Start with the "a few details before we begin" section and then scroll down to "Custom Certificates" If you have any questions, tell me the url that you want to use to access the server and I will tell you how to set the server name, Local TLD, and certificate.
  15. Excellent, sounds like you are back up and running!
  16. @Outcazt @RoiIf you are asking for help I will need to see your diagnostics.zip file (from Tools -> Diagnostics, or by typing `diagnostics` at an SSH prompt.) If you can get it from 6.10.1 that would be ideal, otherwise from 6.9.2 would still be helpful. Also post the exact url (starting with either http:// or https:// ) that you are trying to use, and the exact behavior you are seeing (error message? can't login using a password you are sure is correct?)
  17. Is your server in the DMZ? You don't want it there, it should be on your internal network. Please upload your diagnostics (from Tools -> Diagnostics)
  18. When are you able, please connect a monitor to the server and see what the error message is
  19. Not sure between yesterday and today, it may have been a browser caching issue causing confusion
  20. We might need to work on that wording. If you access this url: http://<server-name>.<local-tld>/ * If Use SSL is no - the login screen will render at that url (http, no cert) * If Use SSL is yes - you will be redirected to https://<server-name>.<local-tld>/ (https, self-signed cert) * If use SSL is auto - you will be redirected to https://[lan-ip].[hash].myunraid.net (https, full cert) If at any point you try logging in and can't even though you are using the right password, clear your browser's cache. Browsers get confused when you enable/disable SSL.
  21. Yes I added you to a group here in the forum, need to investigate why you weren't in it
  22. Hi @ZKWolf we've resolved the issue with your cert. Please open a web terminal and run: rm /boot/config/ssl/certs/certificate_bundle.pem then press Provision again. Your url should change to https://hash.unraid.net:9443
  23. Can you confirm whether or not this is still happening in Unraid 6.10.1 ?
  24. Interesting. It sounds like there was an issue with the plugin installation, in which case the reboot (after upgrading to 6.10.1) is what solved it. I'll keep an eye on this, thanks