Results of unraid-api report -v:

 

<-----UNRAID-API-REPORT----->
SERVER_NAME: TresCommas
ENVIRONMENT: production
UNRAID_VERSION: 6.11.1
UNRAID_API_VERSION: 2.54.0
UNRAID_API_STATUS: running
API_KEY: valid
MY_SERVERS: authenticated
MY_SERVERS_USERNAME: jackfalveyiv
CLOUD: 
        STATUS: [ok] 
        IP: [x.x.x.x] 
RELAY: 
        STATUS: [connected]  
MINI-GRAPH: 
        STATUS: [connected]
SERVERS:
        ONLINE: TresCommas[owner="jackfalveyiv"]
        OFFLINE: 
ALLOWED_ORIGINS: http://localhost, http://IPV4ADDRESS, https://IPV4ADDRESS, http://trescommas, https://trescommas, http://trescommas.local, https://trescommas.local, https://IPV4ADDRESS.HASH.myunraid.net
NCHAN_MODE: nchan
</----UNRAID-API-REPORT----->

 

I should note, I can't access the console via http://trescommas, https://trescommas, http://trescommas.local, https://trescommas.local, or the new url https://ipv4address.hash.myunraid.net in ALLOWED_ORIGINS, but my old link using https://hash.unraid.net is working fine, just alerting me to an unexpected character in the  My Servers dropdown.

Edited December 12, 20223 yr by jackfalveyiv

Would you please

12 minutes ago, jackfalveyiv said:

I should note, I can't access the console via http://trescommas, https://trescommas, http://trescommas.local, https://trescommas.local, or the new url https://ipv4address.hash.myunraid.net in ALLOWED_ORIGINS, but my old link using https://hash.unraid.net is working fine, just alerting me to an unexpected character in the  My Servers dropdown.

 

Ah, in your other message you said "everything seems to be working" so I thought the certificate change had worked.

 

Please get your diagnostics.zip file (from Tools -> Diagnostics) and upload it here.

Sure thing, here it is, appreciate your help!

trescommas-diagnostics-20221212-1452.zip

On the Settings -> Management Access page, do you see any errors/warnings about DNS Rebinding? 

 

The issue is your network is has DNS Rebinding enabled for the myunraid.net domain. You must have previously disabled that feature for the unraid.net domain, you need to do the same thing now for the myunraid.net domain.

 

If you don't remember what you did previously, try doing a Google search for "[router brand] dns rebinding".

 

This was mentioned in the OP here:

  https://forums.unraid.net/topic/132136-update-your-legacy-ssl-certificate-now/ 

 

and there are comments from other users in that thread that may be helpful as well.

I don't see any errors about DNS Rebinding in Settings -> Management Access.

 

Interesting, I do have DNS Rebinding enabled on my Verizon router but there are no specific allowances or exclusions.  I'll keep digging, appreciate the breadcrumbs.  

On 12/12/2022 at 7:05 PM, jackfalveyiv said:

I do have DNS Rebinding enabled on my Verizon router

 

DNS Rebinding prevents a DNS lookup from resolving to a local IP address. It has to be disabled in order for an unraid.net or myunraid.net url to point to your server. On some routers you can disable it for specific domains, on others it is an all on/off setting.

 

Depending on your setup, another option would be to locally set a DNS record that points xxx.hash.myunraid.net to the right local IP. But if you forget that you did that it becomes very difficult to troubleshoot down the road