-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Refused when accessing web ui #160
Comments
Firmware Version? |
Is there a way to find that? I couldn't remember, but it was whatever came with the card that was shipped with the full nanokvm. I haven't flashed to update, other than maybe use the webui to update in early November. |
I have the same issue. I could update the firmware after some problems under 1.2.1. But with the newer 1.3, I could not get the webUI. With 1.2.1 I could login and see the webui. I got my new NanoKVM Lite yesterday. |
Experiencing the same issue. |
Thanks for the workaround. Got my Lite and was a painful start. Didn't know I needed to supply and SD card, just saw it boot looping. Once I found out I needed a card, I installed latest and got this issue. Still don't understand the different versions. After installing 1.2.1, I opened UI and it wanted to upgrade from 1.0 to 2.1. |
1 similar comment
Thanks for the workaround. Got my Lite and was a painful start. Didn't know I needed to supply and SD card, just saw it boot looping. Once I found out I needed a card, I installed latest and got this issue. Still don't understand the different versions. After installing 1.2.1, I opened UI and it wanted to upgrade from 1.0 to 2.1. |
same issue, had to flash 1.2.1 |
So, I got my other nanoKVM back that didn't have issues. Was on loan to a buddy. Confirmed no update was put on it since on loan, it's running: My best assumption is that the problematic one has the same exact image version and webapp version since I received and configured identically, other than have a different hostname. Anyway, second device seems to be running fine. The first one I reported with issues still had the problem. So, now that I had some comparison, I took the sdcard out and attempted to flash 1.3.0 but for some reason both Belana Etcher and Rufus would not read the image file downloaded from github. Flashed 1.2.1 (which appears to be the same version already on both devices). First device booted no issue. I'm still not sure what's up with that but reflashing 1.2.1 seems to fix it. Based on this thread, seems like similar outcomes from other people. It did update the webapp to 2.1.1 (was 1.0.0 on fresh flash). I'm keeping the second device on webapp 2.0.9 for now. |
Having the same issue after updating to 1.3.0. |
I'm getting a connection refused when trying to access the web ui on a browser. I can ping ok. can ssh to the device. Tried switching from http to https (and generating self-signed certs) but it just says connection refused.
Tried to disabled tailscale in case it was interfering, nope. Tried on a different network, nope. Access via tailscale, nope. Somehow the webserver just isn't responding or refusing. But ping and ssh continues to work either way (local or tailscale ip).
The text was updated successfully, but these errors were encountered: