Knownhost and CPanel logins and ports

Dan

Moderator
#1
I thought it would be handy to have the various Knownhost and CPanel logins and ports all in one place so here we go.

If I miss any please let me know and we'll get them added.

Disabling root access will not affect your VZPP or WHM login but it will affect your root FTP login.

Knownhost logins:
Billing: https://my.knownhost.com
User: email you registered with them
Pass: pass you had set up on your account originally (unless you changed it)


Support: https://support.knownhost.com
User: email you registered with them
Pass: pass you had set up on your account originally (unless you changed it)

VPS logins:
Virtuozzo Power Panel: http://server.ip.#:4643
User: root
Pass: pass you had set up on your account originally (unless you changed it)

SSH: I use putty for SSH access.
Server name or IP#
Port: 2200
Connection type: SSH
That should make your connection then you need:
Login as: root
Pass: pass you had set up on your account originally (unless you changed it)

FTP: This will give you FTP access to your whole server
Host address: your server name or IP#
Connection: SSH
Port: 2200
User: root
Pass: pass you had set up on your account originally (unless you changed it)

WHM logins:
Insecure: http://server.name.com:2086, or http://IP#:2086, or http://server.name.com/whm, or http://IP#/whm
Login as: root
Pass: pass you had set up on your account originally (unless you changed it)

Secure: https://server.name.com:2087 or https://IP#:2087, or http://server.name.com/securewhm, or http://IP#/securewhm
Login as: root
Pass: pass you had set up on your account originally (unless you changed it)

CPanel logins:
Insecure: http://domain.name.com:2082, or http://server.name.com:2082, or http://IP#:2082, or http://domain.name.com/cpanel, or http://server.name.com/cpanel, or http://IP#/cpanel
Login as: username created for the domain
Pass: pass created for the domain or your root/reseller pass.
NOTE: If you use your root/reseller password there will be red text telling you so and there will also be a drop box allowing you to change domains. Logging in this way gives you access to everything except their email which you will need to use the user’s pass to access.

Secure: https://domain.name.com:2083, or https://server.name.com:2083, or https://IP#:2083, or http://domain.name.com/securecontrolpanel, or http://server.name.com/securecontrolpanel, or http://IP#/securecontrolpanel
Login as: username created for the domain
Pass: pass created for the domain or your root/reseller pass.
NOTE: If you use your root/reseller password there will be red text telling you that you are logged in using the reseller password and there will also be a drop box allowing you to change domains. Logging in this way gives you access to everything except their email which you will need to use the user’s pass to access.

Webmail logins:
Insecure: http://domain.name.com:2095, or http://server.name.com:2095, or http://domain.name.com/webmail, or http://server.name.com/webmail, or http://IP#:2095, or http://IP#/webmail
Login as: username created for the domain
Pass: pass created for the domain
NOTE: This will give you access to webmail for all email accounts on the domain not including sub-folders.

Secure: https://domain.name.com:2096, or http://server.name.com:2096, or https://IP#:2096
Login as: username created for the domain
Pass: pass created for the domain
NOTE: This will give you access to webmail for all email accounts on the domain not including sub-folders.

Webmail for users created on the domain:
Paths as given above
Login as: username@domain.com
Pass: pass created for the user

Mailman logins:
http://domain.com/mailman/, or http://server.name.com/mailman/, or http://IP#/mailman/
Login as: username created for the domain
Pass: pass created for the domain
NOTE: Unable to confirm on my server as mailman is disabled.

Interchange logins:
http://domain.com/interchange/, or http://server.name.interchange/, or http://IP#/interchange/
Login as: username created for the domain
Pass: pass created for the domain
NOTE: Unable to confirm on my server as interchange is disabled.

Interchange 5 logins:
http://domain.com/interchange-5/, or http://server.name.interchange-5/, or http://IP#/interchange-5/
Login as: username created for the domain
Pass: pass created for the domain
NOTE: Unable to confirm on my server as interchange is disabled.

FTP logins:
ftp://domain.com, or ftp://server.name.com, or ftp://IP#
Login as: username create for the domain
Pass: pass created for the domain

FTP logins for users created on the domain:
Paths as given above
Login as: username@domain.com
Pass: pass created for the user
 
#2
Good work but you might want to make one slight change, it should never been encouraged to login to WHM using the non-secure port, specially when using root.

Neil
 

Dan

Moderator
#3
I agree completely Neil, I have disabled access via non SSL ports in WHM myself although I just noticed that I can still access it through normal means yesterday while doing this write-up.

So remember to use the secure logins people :)
 
#4
how to block certain ports

Ok, so I won't be using email on my servers other than just sending alerts from the server to me. So can I go ahead and block all mail ports incoming?

would I just remove them from the /etc/csf/csf.conf file in the section:
Code:
# Allow  incoming TCP ports
TCP_IN = "20,21,22,25,53,80..."
would those connections be blocked...but I am still able to receive server alerts?

thanks for your time,
Mike
 

Dan

Moderator
#5
Hi Mike,

Those are incoming ports not outgoing so yes your server should still be able to send email out.
 
Top