Please Help / Lost access to SSH / Lost Web GUI / Unsure what happened / Debian GNU-Linux WEB at URL / SSH Resets

  • Looking for some help please.


    I had a working OMV6 (I know 7 is out and I was planning to upgrade soon) and my backup is rather old (IRL got in the way)


    I was having issues with slowdown and lots of hard drive access, so I figured it was busy and left it be for approx 48 hours, all my containers in docker were still working, could still access portainer, etc.


    But I decided to do the same thing I've done before, tapped the power button to allow it to shut down, I waited and it did power down.


    When I powered it back up, I still couldn't access it All other items started up again, all my docker containers, etc.


    I connected the unit to a keyboard and HDMI so I can see the log in screen, but the details have changed.


    my original IP/Port I had set to http://192.168.1.65:85/ but it has changed to http://192.168.1.109:9090/ which gives me this below. which won't take my usual username and password.



    My SSH port, I had changed from the default and used to access it via Putty.

    I have tried to login with my usual admin and PW, but the login screen I'm seeing from the monitor appears to reset/refresh back to the login screen.


    I was going to try omv-firstaid , but with not being able to get to login, I don't know what to do.


    Can anybody help me please?

    Thanks


    edit, realized my original post I put OMV5 to 6, I'm actually on 6, yet to move to 7... doh... guess coffee hadn't kicked in.

    Don't jump, if you do, you'll only fall and hurt yourself.

    Edited once, last by pjghangouts ().

  • Addendum, I had a realization, I can actually still SSH into it by changing the putty details to x.x.x.109 and I can access omv-first aid, I tried option 1 to make sure DHCP it still set, as I have the MAC in my router, but it still come back at x.x.x.109

    Don't jump, if you do, you'll only fall and hurt yourself.

    • Official Post

    if you can ssh into x.x.x.109, you need to access the web interface on the same IP. Did you try the new address with port 85?

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I went into omv-firstaid and I forced the IP address of x.x.x.65 and 8.8.8.8 for the DNS, etc and now I'm able to get into the regular web interface again http://192.168.1.65:85/#/dashboard [I could still access portainer while it was borked, so I had to stop all the containers, it was taking too long to fire up to give errors] but I still see https://192.168.1.65:9090/ which I can't access with either root and openmediavault or my regular details, so I don't know what that is about?


    I had the MAC stored in my router, and when I tried to use DHCP I was getting x.x.x.109, I'm wondering if the router is going on it's last legs?


    I'm going to try omv-firstaid again and put the network back to DHCP, just to see what happens, knowing I can get it back to a working state again. But I'm open to possible checks from a knowledgeable person to maybe give me some logs that might tell me?


    I'm still stumped as to why it decided to bork on me for no reason (or nothing I'd done with that last 24-48 hours anyways)

    Don't jump, if you do, you'll only fall and hurt yourself.

  • So, running omv-firstaid and setting to DHCP puts my IP address back to x.x.x.109 to be able to SSH into that using putty again.


    I'm confused.


    edit, running ifconfig gives me the same mac details as the router has set in the LAN settings, I'm thinking the router is dying?


    enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.1.109 netmask 255.255.255.0 broadcast 192.168.1.255

    ether 08:62:66:49:46:1d txqueuelen 1000 (Ethernet)

    RX packets 348175 bytes 404761479 (386.0 MiB)

    RX errors 0 dropped 0 overruns 0 frame 0

    TX packets 231658 bytes 148381727 (141.5 MiB)

    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    Using that IP x.x.x.109:85/#/dashboard also gets me into the dashboard... Hmmmmm



    I think I'm going to powercycle the router once wifey is done with her gaming, and see if the router had a blip before I even think about anything else

    Don't jump, if you do, you'll only fall and hurt yourself.

    Edited 2 times, last by pjghangouts ().

  • Well, guess it was a router thing, I power-cycled, on DHCP it got the correct IP, I made sure OMV6 was up to date (yet to update to 7) turned everything off except portainer and pihole and did a backup and verify, rebooted and turned everything back on, I guess my Wednesday was meant to be that way. ;)

    Don't jump, if you do, you'll only fall and hurt yourself.

    • Official Post

    I think I'm going to powercycle the router once wifey is done with her gaming, and see if the router had a blip before I even think about anything else

    If networking is acting up and a server reboot doesn't solve it, rebooting your router is a good second action to be take. Beyond that, where consumer routers are concerned, a router reboot once every two or three months is not a bad idea.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!