• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

SSL does not work for subdomains

To protect all subdomains in a subscription with one certificate, you should consider purchasing a multi-domain (a wildcard) SSL certificate.
 
To protect all subdomains in a subscription with one certificate, you should consider purchasing a multi-domain (a wildcard) SSL certificate.
Good. I have a domain, such as google.com, and there is a subdomain sub.google.com. There are 2 different certificate. How do I do to open sub.google.com? When I open https://sub.google.com, it opens google.com. Prompt consistently how to do please.
===
Хорошо. У меня есть домен, к примеру google.com, и есть субдомен sub.google.com. Есть 2 разных сертификата. Как мне сделать, чтобы открывался sub.google.com? Когда я открываю https://sub.google.com, то открывается google.com. Подскажите последовательно, как правильно сделать пожалуйста.
 
opened as a subdomain https://google.com/sub
And I have discovered how to https://sub.google.com

A subdomain is configured as a subfolder.

More ceased to open https: // localhost: 8443
Opens the panel only as http: // localhost: 8880
How to fix?
===
субдомен открывается как https://google.com/sub
А мне надо чтобы открывался как https://sub.google.com

Субдомен настроен как вложенная папка.

Еще перестал открываться https://localhost:8443
Открывается панель только как http://localhost:8880
Как исправить?
 
opened as a subdomain https://google.com/sub
And I have discovered how to https://sub.google.com

A subdomain is configured as a subfolder.

Just add subdomain as subdomain but not as subfolder - http://download1.parallels.com/Plesk/PP12/12.0/Doc/en-US/online/plesk-administrator-guide/65180.htm

More ceased to open https: // localhost: 8443
Opens the panel only as http: // localhost: 8880
How to fix?
Maybe it is firewalled or Plesk service is not started or something else? Have you checked it at least? Have you tried troubleshoot it with reading logs, etc? Any results of troubleshooting?
 
I created a sub-domain as a physical hosting:
sub.google.com
Still https://sub.google.com not working.
When open https://sub.google.com, it opens the contents https://google.com

To access the contents of https://sub.google.com - I should point out: https://sub.google.com/sub_google_com

This address https://sub.google.com/sub_google_com not very comfortable.
How to make https://sub.google.com?
===
Я создал субдомен как физический хостинг:
sub.google.com
По прежнему https://sub.google.com не работает.
Когда открываю https://sub.google.com, то открывается содержимое https://google.com

Чтобы открыть содержимое https://sub.google.com - мне надо указывать: https://sub.google.com/sub_google_com

Такой адрес https://sub.google.com/sub_google_com очень не удобный.
Как сделать сделать https://sub.google.com?
 
Back
Top