I just updated my SG300-28P to the latest firmware, 220.127.116.11, after previously running 18.104.22.168.
Previous to the update, I could access the Web interface with the hostname I'd specified in System Settings (as part of the FQDN I use for my LAN), i.e. https://switch1.domain.com (where switch1 is the hostname set in System Settings, and the rest is the search domain I use on my LAN).
Following the update, any attempt to access it by hostname results in a long pause whilst it is "waiting for switch1.domain.com", before finally going to a blank page with only the opening <html> tag of the page loading as content if I view the source. Nothing else loads. I can view certificate information so it is obviously getting a response, but grinding to a halt before it gets any further. If I access the Web interface using IP address, it connects fast and without any problem.
Worth mentioning, I can still ping / SSH to the switch using the hostname / FQDN, so I don't think it's a networking issue, just that the Web interface has stopped loading for hostname requests. I've also tried clearing the browser cache and using different browsers on different machines, but it's the same for all.
The switch's logs do not show any connection attempts at all when using hostname but do show successful connects when I use the IP.
Has anyone got any ideas? Thanks!
We also have this same issue on an SG300-10P.
using curl the web server clearly behaves differently
$ host ssw01.c.home
ssw01.c.home has address 10.0.1.6
$ curl http://ssw01.c.home
$ curl http://10.0.1.6
This document has moved to a new <a href="http://10.0.1.6/cs2cd811e/">location</a>.
Please update your documents to reflect the new location.
yes since it works with IP, not with domain name
check the bug and it shows fixed with the newer version
@balaji.bandi- The most recent release (1.4.11.02, 16th October 2019) fixes CSCvp23218, but does not fix the 'domain vs IP' issue people are reporting here. The domain / IP issue was actually introduced with the most recent release.
The amount of time I tried fixing this myself, thinking the flash somehow was broken I could have just bought another switch...
Also the remote exploit they fixed... I don't want to know how they did it if it is the cause of this bug.
This issue appears to have been semi-fixed by the recent v22.214.171.124 firmware release. I say "semi-fixed" as now on navigating to the switch FQDN a HTTP 302 redirect is issued to the switch management IP address. So yes, it works again via FQDN, but your browser is redirected to the IP address.
Same here, on four SG-300 series switches: 2x 10, 1x 10P, 1x 20, FW 126.96.36.199
If I browse to the switch using the FQDN, by http or https, my browser gets redirected to the IP address of the management interface.
I confirmed by downgrade that variable's finding is accurate: v1.4.10.06 26APR2019 does not have the issue.
For a switch that's out of software support, it sure would be nice if the latest (last?) FW didn't have the issue. Here in late March 2020, the newest version is 1.4.11.04 29JAN2020.
No way is this a justifiable reason in and of itself for a hardware refresh, but it's still really annoying.
Same for me, I've noticed it with the very latest version (jumped from 188.8.131.52 to 184.108.40.206)
Pretty anoying for me as I generated SSL certificates for FQDNs only...
I hope this will (can) be fixed since the vulnerability ;-)