Common problems after opening the panel certificate

aaPanel_Jose

Common problems after opening the panel Https:

1. Browser shows no trust
If you choose a self-signed certificate, the browser will show no trust, please change to the Let's Encrypt certificate.

2. Unable to access after opening the panel
You can turn off SSL by manually entering the following command on SSH.
rm -f /www/server/panel/data/ssl.pl && /etc/init.d/bt restart

suricloud

I just updated to this latest version.When i click to confirm to install Let's encrypt ssl i get a message of "please bind your domain to the panel" I already created hostname.domain.com in the website /sitemanager. What should i do more?

aaPanel_Jose

suricloud please open the panel settings, which can bind the domain name

suricloud

Thanks, its working now 🙂
Very nice to see Aapanel is imrpoving fast.

suricloud

Hi,after i activated ssl for the panel now i see apache stop running.If i try to start or restart apache i get this error.
What to do ?

aaPanel_Jose

suricloud
please runpkill -9 httpd and start again

suricloud

Not working,getting the same errror again.

aaPanel_Jose

suricloud This error is that there are other processes occupying ports 443.
Use this command to check which process is taking up 443
netstat -ntulp|grep 443

thiagotgc

I'm using Ubuntu 18, in the latest version of aaPanel, and I get this message.

aaP_pablo

Hi!
I just installed aaPanel on my server and got the same problem that thiagotgc on 24 May 2020.

When Im trying to enable SSL on the panel, jumps the same small error window. I don't know how to solve it.

Any solution?

thiagotgc

Now I was able to install SSL to access the panel.

However, only after creating a WebSite with the same name Domain used in Settings.

aaPanel_Jose

thiagotgc
I just used the brand new ubuntu18 test, and no error was reported. . I will continue to pay attention to this issue

CQT

Hello Jose, the same error arises for me with CentOS 7 and 8 and Ubuntu 18.04

aaPanel_Jose

CQT

Can you send me the server panel in question to try?
Or you press f12, find the network label to see what data is returned by the SetPanelSSL interface

yashris

https://prnt.sc/ukoi4q

aaPanel_Jose

yashris

Hello, any update on this?
I am receiving this error as well after my domain name SSL was expired

aaPanel_Jose

yashris
I just tried the setup on the test server and it worked fine
can i login to your panel to check? if possible, please send your login info to jose@aapanel.com

GIJENTHIRA

how can i use my custom SSL sir?

aaPanel_Jose

GIJENTHIRA
Paste your certificate into other certificate tabs and save
https://doc.aapanel.com/web/#/3?page_id=138

Enigma
did you mean domain2 is using the wrong certificate?
have you try to reset the domain2 ssl？

Enigma

Hi, I have 2 domains. Both using positive ssl. Domain 1 for aaPanel and domain 2 for the site. When accessing Domain 2 there is an error "Your connection is not private". After checking the domain 2 still using the domain panel certificate 1. How to fix it? OS: Centos 8.

Enigma

aaPanel_Jose did you mean domain2 is using the wrong certificate?
have you try to reset the domain2 ssl？

Yes that's right, domain 2 using domain 1 certificate when accessed in browser. How do I reset it? it happened when I access domain 2 with www. If access domain 2 (https://domain.tld) without www there is no problem. Tried turn on and turn off site, disabled and enabled SSL but still have not secure message, DNS zone also has A record www pointing to right IP Address.
I use the Chrome browser.

Enigma

Enigma
Here are details.
As suggested aaPanel, after initial install aaPanel to change everything on setting. Previously I changed default site dir www/wwwroot to www/otherfoldername

I'm using nginx 1.17.10, php 7.4, Positive SSL, Forced Https ON, DNZ Zone A record www pointing to ip address, CNAME www pointing to domain.tld.

After checked. When user entry domain 2 in browser have various result:

domain2.tld >> Secure. Auto forward to https://domain2.tld
www.domain2.tld >> Not secure - 403 Forbidden. Not auto forward to https
http://domain2.tld >> Secure auto forward to https://domain2.tld
http://www.domain2.tld >> Not secure - 403 Forbidden. Not auto forward to https
https://domain2.tld >> Secure
https://www.domain2.tld >> Not secure. invalid/wrong certificate or domain1.tld certificate

When checked domain 1 in browser, everything is OK and autoforward to https except when user entry http://www.domain1.tld have result 403 Forbidden and not auto forward to https.
Other subdomain host.domain.tld with let's encript is OK and autoforward to https

So I have 3 problems.

Wrong SSL on domain2.tld
Not auto forward to https on both domain1.tld and domain2.tld
Not secure - 403 Forbidden on both domain1.tld and domain2.tld

What's wrong?
I hope when user entry domain.tld or www.domain.tld by http or https, browser will display secure page and auto forward to https. Thanks.