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

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?

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

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

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 ?

suricloud please run pkill -9 httpd and start again

Not working,getting the same errror again.

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

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

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.

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

Common problems after opening the panel certificate

aapanel_power

maxmah Hello, it looks like this site is properly visited by maxmah.net

aaP_hardxman

I set up the "Domain" field on the setting page to FQDN.
I can Turn on Panel SSL.
Please check your config.

aaP_ti_growup

I got "Type error: nonetype objetct is not subcriptable"
already tried to change aapanel port and didn't work.
already tried fix button and didn't work.

please, help!

ashu

I am also getting same Type error: nonetype objetct is not subcriptable while applying panel ssl certificate

aaP_estartoken777

UBbuntu 22.04 Apache2 install. cat: /www/server/panel/install/apache/config.pl: No such file or directory
apache.sh: line 225: cd: /www/server/apache/src: No such file or directory
apache.sh: line 226: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.

aaPanel_Kern

aaP_estartoken777

Hello, is it normal to try to install again now?

aaP_qweths14

aaPanel_Kern

Hello, is it normal to try again now?

aaP_qweths14

aaP_hprj

aaP_qweths14 i am facing same issue no self signed certificate installation working..

aaPanel_Kern

aaP_hprj
Hello, is it normal to try again now?

aaP_naeem

adding Let's Encrypt to aapnel domain gives error?

aaPanel_Kern

Hello, it works. It is recommended that you use a brand new subdomain name.
If there is an error, you can try to apply for SSL from the website list. Then copy it to the settings and paste the content into Panel SSL.

aaP_naeem

aaP_nicacio_tecnologia

hello, it works.
I'm having trouble setting up SSL on the panel; it's giving the following error:
77.228.208: Invalid response from https://aapainel.starsyst.online/.well-known/acme-challenge/VCZeye0-YULr2MIJJ3JgJl9SvVKfCq_00OfnaIEoYa4: 404

aaP_nicacio_tecnologia

domain [aapainel.starsyst.online] Apply SSL certificate Error: ['Verification failed, domain name resolution error or verification URL cannot be accessed! ', {'identifier': {'type': 'dns', 'value': 'aapainel.starsyst.online'}, 'status': 'invalid', 'expires': '2026-03-08T17:27:08Z', 'challenges': [{'type': 'http-01', 'url': 'https://acme-v02.api.letsencrypt.org/acme/chall/3106456052/666436557412/JublsA', 'status': 'invalid', 'validated': '2026-03-01T17:27:40Z', 'error': {'type': 'urn:ietf:params:acme:error:unauthorized', 'detail': '187.77.228.208: Invalid response from https://aapainel.starsyst.online/.well-known/acme-challenge/f0N293qQl4LCLiFR9bdYfsGNGJMw71sw1NssSsOxBS4: 404', 'status': 403}, 'token': 'f0N293qQl4LCLiFR9bdYfsGNGJMw71sw1NssSsOxBS4', 'validationRecord': [{'url': 'http://aapainel.starsyst.online/.well-known/acme-challenge/f0N293qQl4LCLiFR9bdYfsGNGJMw71sw1NssSsOxBS4', 'hostname': 'aapainel.starsyst.online', 'port': '80', 'addressesResolved': ['187.77.228.208'], 'addressUsed': '187.77.228.208'}, {'url': 'https://aapainel.starsyst.online/.well-known/acme-challenge/f0N293qQl4LCLiFR9bdYfsGNGJMw71sw1NssSsOxBS4', 'hostname': 'aapainel.starsyst.online', 'port': '443', 'addressesResolved': ['187.77.228.208'], 'addressUsed': '187.77.228.208'}]}]}]

aaPanel_Kern

Hello,
Is the problem solved?
If you cannot use http verification, you can try to use dns verification.

aaP_nicacio_tecnologia

« Previous Page