• 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

Resolved Plesk Onyx Preview and FeedBack

Status
Not open for further replies.
I wanted to edit my answer, but I saw new posts.
What about an option to NOT expose docker ports? I don't want my mongodb to be exposed to the world

If it can help (I doubt it), webmail is working fine for me :)
 
I 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
 
Is this webmail hostname resolvable from outside? Check it with

# host webmail.domain.com
# dig +trace webmail.domain.com

Yes, its working. Now i don't know why, the error has changed o_O

"504 Gateway Timeout: remote server did not respond to the proxy"
But not only for webmail, for domain.com too

:confused:
 
What about

# plesk repair web

?

Already donde with "plesk repair all", but I will do this. Result:

Error messages: 0; Warnings: 0; Errors resolved: 0

:confused::confused:

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
 
Last edited:
Already donde with "plesk repair all", but I will do this. Result:



:confused::confused:

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

DONE!

I repaired it. The problem was the "DNS A" (Still don't know why). After, the page dosent work because after rebooting the server, firewalld was active and blocking al connections. I stoped firewalld and everything was working :)


Many Thanks @IgorG for your help. You are my hero :p
 
hi fellas,
i restart the server and nginx won't start,

so i run nginx -t

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] bind() to 158.69.XX.XX:443 failed (99: Cannot assign requested address)

it's a bug?

so i reread Ips again and nginx start
 
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?
 
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.
 
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.
AHHH, cant believe i forgot to turn that off once I installed CentOS. Usually the first thing I do. Thanks !!
 
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?

From several days testing Onyx with several wordpress sites, so far so good.

I did not had these problems on fresh CentOS 7.2 install.
 
I did not had these problems on fresh CentOS 7.2 install.

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. ;)

The initial mode for a SELinux - installation on CentOS - based systems are documented ( Reference: => https://wiki.centos.org/HowTos/SELinux ) as:
SELinux has three basic modes of operation, of which Enforcing is set as the installation default mode.
 
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. ;)
I have just checked and selinux is installed and active.
 
Error after Installtion where i Setup Plesk admin Password. Also on Licence section.
Ubuntu 16.04

Internal error: StatInfo->getProductVersion failed: sysinfo failed: sysinfo: get_device: Cannot chdir to /var/lib/lxcfs System error 22: Invalid argument
Message StatInfo->getProductVersion failed: sysinfo failed: sysinfo: get_device: Cannot chdir to /var/lib/lxcfs System error 22: Invalid argument
File functions.php
Line 89
Type PleskFatalException
 
Status
Not open for further replies.
Back
Top