Dani Junsui
New Pleskian
The page show an "ERR_NAME_NOT_RESOLVED" but the DNS for webmail.domain is correct (A to IP)What do you mean exactly? Do you have any error messages, or what?
Thanks
The page show an "ERR_NAME_NOT_RESOLVED" but the DNS for webmail.domain is correct (A to IP)What do you mean exactly? Do you have any error messages, or what?
Have you checked this article https://kb.plesk.com/en/118259 ?The page show an "ERR_NAME_NOT_RESOLVED" but the DNS for webmail.domain is correct (A to IP)
Have you checked this article https://kb.plesk.com/en/118259 ?
add Plesk server to the list of DNS servers (contact your registrar);
add respective CNAME DNS entry onto registered name servers.
Is this webmail hostname resolvable from outside? Check it withI have the DNS webmail.domain with the A, and in plesk 12.5 that is working :S
Is this webmail hostname resolvable from outside? Check it with
# host webmail.domain.com
# dig +trace webmail.domain.com
Try to restart Apache."504 Gateway Timeout: remote server did not respond to the proxy"
Try to restart Apache.
What about
# plesk repair web
?
Error messages: 0; Warnings: 0; Errors resolved: 0
Already donde with "plesk repair all", but I will do this. Result:
As I said, I don't mind to reinstall everything and do it step by step again: (Open pots, Install Plesk, install Domain). Maybe this time webmail works... If there are not more ideas to repair all, I'll do that
It is misconfiguration. You can find old KB article about this issue.it's a bug?
AHHH, cant believe i forgot to turn that off once I installed CentOS. Usually the first thing I do. Thanks !!Hi SeanieR,
pls. consider to DISABLE SELinux to avoid such issues on a fresh linux installation. Afterwards, consider to investigate the SELinux policies / log - files and correct the policies, or add correct ones.
fresh install on CentOS 7.2. Apache won't start and getting this in an email alert:
Template_Exception: Can not restart web server: Oct 06 15:26:11 elh9.elive.net httpd[31803]: (13)Permission denied: AH00072: make_sock: could not bind to address [::]:7080
Oct 06 15:26:11 elh9.elive.net httpd[31803]: (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:7080
Oct 06 15:26:11 elh9.elive.net httpd[31803]: no listening sockets available, shutting down
Oct 06 15:26:11 elh9.elive.net httpd[31803]: AH00015: Unable to open logs
Oct 06 15:26:11 elh9.elive.net systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 06 15:26:11 elh9.elive.net kill[31805]: kill: cannot find process ""
Oct 06 15:26:11 elh9.elive.net systemd[1]: httpd.service: control process exited, code=exited status=1
Oct 06 15:26:11 elh9.elive.net systemd[1]: Failed to start The Apache HTTP Server.
Oct 06 15:26:11 elh9.elive.net systemd[1]: Unit httpd.service entered failed state.
Oct 06 15:26:11 elh9.elive.net systemd[1]: httpd.service failed.
file: /usr/local/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 108
code: 0
Forcing a rebuild of the server config files doesnt fix it.
Any suggestions or is it a bug in the build?
I did not had these problems on fresh CentOS 7.2 install.
SELinux has three basic modes of operation, of which Enforcing is set as the installation default mode.
I have just checked and selinux is installed and active.Pls. be aware, that server hosting provider offer often enough own image files for their customers, based on the choosen server type. On a "minimal" server - type - choice for example, SELinux is not installed.