This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[NotaBug] SSH Access first Configuration - Still "Acces denied"

Hello everyone,

just had an interesting phenomenon - perhaps a bug? I just started my very first and initial configuration for the SSH access. Of course, I configured the password for the "loginuser" along with the password for "root" and than clicked to save. Well, I used the same password "123" for both users, just for the first test. The saving worked, both passwords accepted, no errors.

But via the login process over SSH, I only got the message "Access denied" when I tiped in the password. Same problem all the time, for every password-changes - everytime together for "loginuser" and "root". Reboot didn't help.

After changing the password only for "loginuser", then saving and afterwards changing the password only for "root" with saving again, I could successfully log in to the SSH session. [:D]


Hope this helps someone ...

Btw. a bug tracker doesn't exist, does it? [:S]


This thread was automatically locked due to age.
  • After setting a distinct and "complex" password for loginuser, I finally got ssh2 access. 

    The following password worked: Password123
  • After updating to  9.315-2 from ISO 9.313-13, I was once again confronted with the SSH2 login problem.

    After trying a few dozen combinations of password resets for "loginuser", I finally got in.  

    Something isn't right.  

    The SSH log shows nothing more than the following:
     Failed password for loginuser
  • I am also experiencing a similar SSH issue. I have tried changing both passwords for root and loginuser to different, complex, one at a time, both at the same time etc...

    and each time I try loginuser I always see "Failed password for loginuser from......"

    Something seems to be not quite right with this. I will try with the keys but wanted something simply for my tests.

    I am using the ASG software, Firmware version:  9.315-2 

    Michael.


    EDIT
    ------------

    After numerous changes to passwords my final issue was due to the allowed networks. I thought Internal would just allow only SSH from my network but this doesn't appear so, so I have put this back to ANY (which I am not comfortable with).
  • BHL, "Internal (Network)" should work.  Are you certain that you didn't have "Internal (Address)" instead? For access from outside, I also add "myusername (User Network)" so that I can get in via a Remote Access client.

    Cheers - Bob
  • Thanks Bob, I was almost 99% sure that's the network I had listed but I have removed the 'All' and added 'Internal (Network)' and it works as expected. 

    Good idea about username remote network too.

    Thanks,

    Michael.
  • Hi Guys,

     

    Thanks for the info. I still couldn't get it to work even after changing each password one at a time. But after making both passwords different and also different from my other UTM passwords it worked right away.

    Couldn't log in with loginuser at all before doing this.

     

    Thanks :)

  • Iced_Earth... you are a freaking genious!

    I was going nuts over this isssue... couldn't login with "loginuser" over SSH despite re-setting the Password over and over and over again...

    Until I've stumpled upon your hint "After changing the password only for "loginuser", then saving and afterwards changing the password only for "root" with saving again, I could successfully log in to the SSH session. [:D] "

    This did it for me!

    The very sad part is: I'm running the latest 9.412-2 - almost three years after your post...

  • This is not fixed at all. Password based login for loginuser is still not working in 9.501-5

    The workaround with only setting the password for loginuser doesn't work anymore as well.

    I can work around this problem with key based ssh login (which is more secure anyway), BUT the bug is STILL not resolved!