Cisco Business 220 Series web UI ERR_CONNECTION_REFUSED

[s66903]

Hello All,
New to the forums here so hopefully in the right spot!

I got off of amazon a new Cisco Business 220 Series switch and when going to the web UI after initial setup it worked fine.

Fast forward some hours later I need to go back in to make more changes I get met with an error when going to the Switch's IP in the browser - "ERR_CONNECTION_REFUSED"

I had factory reset the switch the first time this happened and started over only to be met with the same fate later on again.

I was hoping to find here on the forums any feedback on how to fix this issue. I am new to cisco and not fully familiar with CLI stuff so if that is suggested if you don't mind sharing steps would be great or linked resources.

The switch itself is up and the network is working fine, just the config page is having an issue.

The URL bar with the IP starts with HTTPS changing it to HTTP does not help either
Rebooting the switch doesn't help either

[s66903]

Looks like someone else had the same issue and was only suggested to reboot
https://community.cisco.com/t5/switching/unable-to-access-the-web-ui-on-cisco-cbs220/td-p/4690011

Any other suggestions?

[Richard Burts]

Am I understanding correctly that if you factory reset the switch that you are able to access it (and repeat the configuration steps)? And in doing the configuration did you create a user ID and password?

If you did create a user ID and password I suggest that you attempt accessing the switch not with the GUI and see if we can find why the GUI is not working. So I suggest these steps:

- from a PC connected to the switch try to ping the switch address (which verifies whether you have basic IP connectivity).

- assuming that the ping was successful, try accessing the switch using telnet. (telnet <switch_IP>), if prompted enter user ID and password. 

- if you have access then try to enter enable mode. (enable) and if prompted enter the enable password.

- use the command show run and post the output.

[s66903]

Hi Rick,

Thanks for this response. Come to find out the culprit was a VM in a Proxmox host that was being given the same IP as the switch from PFSENSE DHCP to that VM while the switch had that particular IP as static.

Once that was corrected it made sense for losing the access to the switch constantly.

I will make another thread soon potentially Im having trouble with speed issues all around on Netgate 6100 paired with this switch. LAN default and VLANS wireless and wired all devices get really bad downloads on various sites / slow loading pages etc.

So I have to isolate that next. But for now, thank you for this here running some ping checks and find out via arp cache table what other device was using that same IP came to be handy. The switch was intermittently pingable when rebooting.

[Richard Burts]

Thanks for the update. Glad that you were able to identify and solve the issue. I look forward to your continued activity in the community.