Topic: Web Panel not accessible

[zenny]

I have installed sme7.2 in one of my machine to test. I am new to SME. Now I am getting problem that I could not even log in to sme-manager from local network except inside the server itself. The admin and the system password combo gives invalid usersername and password error. I tried to change the user-password of admin but it does not allow. Nor I can ssh.

I did several things so far:

1) Added the accessing machine IP in remote access in the panel but in vain ( at par with
2) Added the wireless network range of IPs in the local network without any results
3) Tried to change the password without success (http://forums.contribs.org/index.php?topic=38551.0) even locally.

I checked these pages so far to find out a solution. http://forums.contribs.org/index.php?topic=36529.0 http://bugs.contribs.org/show_bug.cgi?id=2865 http://forums.contribs.org/index.php?topic=35924.0;all and SME admin docs.

All inputs would be appreciated. Thanks.

[electroman00]

1) Added the accessing machine IP in remote access in the panel but in vain ( at par with
2) Added the wireless network range of IPs in the local network without any results
3) Tried to change the password without success (http://forums.contribs.org/index.php?topic=38551.0) even locally.

You should only have to do #1 if accessing from WAN and log in as admin (not root) and your password

Are you logging in with an IP address or FQDN?
Server only or gateway setup?

Posting of ifconfig would be helpful.

[zenny]

I have been logging with IP address. However, the problem to access the server-manager is overcome after I did yum update -y. I am using in server only mode.

However, I could not ssh to the server even from the local network even after I created a new user (since the ssh access to root is disabled in /etc/sshd_config).

Any hints?

[mmccarn]

Check your 'Secure shell settings': http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter11#Remote_Access

You need to have 'Allow administrative command line access over secure shell' and 'Allow secure shell access using standard passwords' both set to 'yes' (until you can set up public/private key authentication...)

There is another option on the server screen that does not show up in the documentation (yet): 'TCP port for secure shell access'.  This defaults to '22', but you can change it.

If you have both of the 'Allow...' options enabled and still cannot access your server on the port specified under 'TCP port...' then you should open a bug report on the bug tracker.