KeyHelp Community

Hello, I have a question. in the KeyHelp panel my hostname is panel.mydomain.com and in my server /etc/hostname server1.mydomain.com

and /etc/hosts
127.0.0.1 localhost
127.0.1.1 server1.mydomain.com
000.00.000.0 (my IP) mydomain.com server1




In Keyhelp Panel

Name server

Here you can change the name servers used for the DNS configuration.
ns.mydomain.com.
ns2.mydomain.com.
ns.panel.mydomain.com.
ns2.panel.mydomain.com.


this is on Ubuntu 22.04

It's this the correct setup??

Normally your panel should have the same FQDN as your server.

You can change the servername within KeyHelp. Have a look at the settings section.

Hi, I believe that there is no need to open new topic and I will use this one because I have one similar problem with panel access.

First of all I would apologize because question is maybe stupid but I'm new with KeyHelp.

I have VPS with Ubuntu 22.04, installed KeyHelp easily following instructions on website.

After instalation I have login info:

- url: server1.domainename.com
- user: adminusername
- pass: password

Problem is that when I open with browser server1.domainename.com I get classic browser error that there is no such website, but when I enter VPS IP address 123.123.123.123 I get login screen for KeyHelp and of course I get SSL error.

When I loged at KeyHelp, checked nameserver, hostname, IP address and everything is correct.

Also checked on server etc/host and hostname - everything is correct.

For now it seems that everything else is working, I have created user and connected server TLD domain, I can access that domain (I get KeyHelp default page), even added SSL certificate (Let's Encrypt) and everything is ok.

Maybe there is some stupid easy solution for this but I can't get think of it.

So to conclude, I would appreciate if someone can help me with simlple solutions for :

- How to resolve problem with control panel access over IP address instead FQDN
- How to add SSL for control panel login when first problem is resolved

Hallo,

there must be an A-record for server1.domainename.com in the responsible nameserver of the domain domainename.com that points to the IP of your server.

Just to add: ^ this above has to be checked at your domain provider.

How to add SSL for control panel login when first problem is resolved

This can be turned on within the admin area of KeyHelp -> "TLS/SSL certificates -> "Secure server services",
or is performed automatically within the first 24h of a fresh install, if the panel domain is correctly resolvable.

Florian wrote: ↑Fri 23. Jun 2023, 09:53 Hallo,

there must be an A-record for server1.domainename.com in the responsible nameserver of the domain domainename.com that points to the IP of your server.

Hi,

I use Namecheap and at my account I have A record for domainename.com, and A record for server1.domainname.com

Same IP address, domainename.com has proper propagation, server1.domainname.com not propagated at all.

Alexander wrote: ↑Fri 23. Jun 2023, 10:08 Just to add: ^ this above has to be checked at your domain provider.

How to add SSL for control panel login when first problem is resolved

This can be turned on within the admin area of KeyHelp -> "TLS/SSL certificates -> "Secure server services",
or is performed automatically within the first 24h of a fresh install, if the panel domain is correctly resolvable.

Ty, I believe that everything will work fine after I resolve problem number one

Maybe you want to reveal your panel URL to let the community here check your DNS settings.

Alexander wrote: ↑Fri 23. Jun 2023, 10:41 Maybe you want to reveal your panel URL to let the community here check your DNS settings.

No problem - server1.connectlyone.co.uk

I'm planing to test some script on TLD meanwhile...

Seems like you only have an A record for "connectlyone.co.uk" but not for any subdomain of "connectlyone.co.uk".
You need to add an A record for "*.connectlyone.co.uk" in your domain provider settings.

Alexander wrote: ↑Fri 23. Jun 2023, 10:53 Seems like you only have an A record for "connectlyone.co.uk" but not for any subdomain of "connectlyone.co.uk".
You need to add an A record for "*.connectlyone.co.uk" in your domain provider settings.

Hm I have A record for connectlyone.co.uk, and A record for server1.connectlyone.co.uk

Two A records at Namecheap advanded DNS settings panel...

host server1.connectlyone.co.uk
Host server1.connectlyone.co.uk not found: 3(NXDOMAIN)

The resolving is not working

Florian wrote: ↑Fri 23. Jun 2023, 10:56 host server1.connectlyone.co.uk
Host server1.connectlyone.co.uk not found: 3(NXDOMAIN)

The resolving is not working

Yeap, but no clue what else to do

Asked Namecheap and they said to give them 24 hours to propagate everything....

If seems to work now. My browser meanwhile has reloaded the tab with your page automatically and it shows a HSTS warning.
Now just switch to Lets Eencrypt (accessing the panel via IP address - "TLS/SSL certificates -> "Secure server services") and everything will work.

Alexander wrote: ↑Fri 23. Jun 2023, 11:06 If seems to work now. My Browser meanwhile has reloaded the tab with your page automatically and it shows a HSTS warning.
Now just switch to Lets Eencrypt (accessing the panel via IP address - "TLS/SSL certificates -> "Secure server services") and everything will work.

Yes, now everything is working....

Ty....sorry for bothering you all....It seems that only Namecheap support needed to contact earlier