Hi,
On my 1830s, running 2.9.1, running local management, I don't experience the redirect to IP address problem.
I used "lets encrypt" certificates on these switches for a while , it worked ok but it's a bit painful as you have to request the certificates on another device, e g. A Debian VM & then convert to correct format & upload the certificates to the switch using the web gui.
There are no apis or CLI on 1830 so the process has to be manually repeated every time the certificate expires.
------------------------------
Travis Thorne
------------------------------
Original Message:
Sent: 06-30-2024 05:27 AM
From: mikael.cogne@salnavigation.com
Subject: Local Management - HTTPS redirects to IP instead of Hostname
Dear All, did this one ever get solved? I have one 1960 (JL805A) which is running firmware 2.9.1.17 (latest one I assume, not the easiest to find for some reason) and in the GUI you have the option to set DNS for the switch which I assume means that thihgs like this will work. But I also have three 1930's and they do not have the DNS server option at all which means NTP etc. won't work with FQDN only IP and hence issues with all other advanced featutures like this that requires DNS. I've tried with the latest firmware (same version number as for the 1960 at 2.9.1.17, I've just tried with an older release (2.8.1.35) but same issue, not possible to configure a DNS server. I even managed to find the config command for it in the config file from the 1960 "ip name-server 8.8.8.8" and added that to the config for a 1930 and tried it but of course no luck there either. I'm currently looking into deploying ADCS with NDES/SCEP which, assuming I get it up and running, won't work due to this. The 1930 series of switches are really nice otherwise as a fairly cheap entry/medium level switch with enterprise features, or so I thought. So any news on when this will be fixed or how to fix it now if that is possible? Thanks
------------------------------
Mikael Cogne
Original Message:
Sent: 06-29-2022 09:49 PM
From: adamh
Subject: Local Management - HTTPS redirects to IP instead of Hostname
We are still waiting on this fix. It causes issues for us as we remotely manage a lot of switches for clients. Is there an ETA on this being fixed in the locally managed firmware?
------------------------------
Adam Harm
Original Message:
Sent: 01-25-2022 06:41 AM
From: Unknown User
Subject: Local Management - HTTPS redirects to IP instead of Hostname
Isn't the 2.5.0 release just for cloud managed switches? Perhaps you mean 1.0.8? If so, when will this be coming?
https://community.arubainstanton.com/browse/blogs/blogviewer?blogkey=8aac4e14-50d9-4991-8c72-602a4d87768d
Original Message:
Sent: 01-24-2022 04:52 PM
From: Jessica Mitchell
Subject: Local Management - HTTPS redirects to IP instead of Hostname
Hi Colin,
The 2.5.0 release will include the new behavior and resolve the issue described.
------------------------------
Aruba Instant On Communications
Original Message:
Sent: 01-18-2022 09:53 AM
From: Unknown User
Subject: Local Management - HTTPS redirects to IP instead of Hostname
Happy 2022!
This issue is still not fixed!!!! What gives????
Original Message:
Sent: 12-15-2020 12:30 PM
From: Unknown User
Subject: Local Management - HTTPS redirects to IP instead of Hostname
Has this issue been fixed? Oh, wait ...... no it hasn't!
------------------------------
Colin Fieldgate
Original Message:
Sent: 10-26-2020 08:43 AM
From: Archive User
Subject: Local Management - HTTPS redirects to IP instead of Hostname
Hi @MrFixit ,
yes, this is not an issue with only HTTPS. The switch redirects to its IP address regardless of whether it is accessed via HTTP or HTTPS. It should not happen either way and I don't understand the reasoning behind the redirect.