• 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

Fresh install with a few issues

T

thelongmile

Guest
Hello!

I'm very new to the world of plesk so I hope you'll help me out with a few problems I've been having.

I've installed Plesk Panel 10.2.0 onto a Clean install of Centos 5.6 x86_64, and I've encountered a couple of issues post installation, This was a 'typical' install rather than a 'complete' one..

The server currently has no domains added to it and is a completely clean installation...

1) Mail from the server isn't sending at all, previously I've installed servers with no domains but a valid hostname (in my case DS142.redstation.com or similar) and the phpmailer has sent mail from that with no issues. I note that this is using qmail, so I ran tail -f /usr/local/psa/var/log/maillog and got the following

Apr 14 16:30:26 h109-73-74-74 qmail: 1302795026.671996 starting delivery 800: msg 172721701 to remote [email protected]
Apr 14 16:30:26 h109-73-74-74 qmail: 1302795026.672007 status: local 0/10 remote 1/20
Apr 14 16:30:26 h109-73-74-74 qmail-remote-handlers[24475]: Handlers Filter before-remote for qmail started ...
Apr 14 16:30:26 h109-73-74-74 qmail-remote-handlers[24475]: [email protected]
Apr 14 16:30:26 h109-73-74-74 qmail-remote-handlers[24475]: [email protected]
Apr 14 16:30:26 h109-73-74-74 qmail-remote-handlers[24475]: hook_dir = '/usr/local/psa/handlers/before-remote'
Apr 14 16:30:26 h109-73-74-74 qmail-remote-handlers[24475]: recipient[3] = '[email protected]'
Apr 14 16:30:26 h109-73-74-74 qmail-remote-handlers[24475]: handlers dir = '/usr/local/psa/handlers/before-remote/recipient/[email protected]'
Apr 14 16:30:41 h109-73-74-74 qmail: 1302795041.696916 delivery 800: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
Apr 14 16:30:41 h109-73-74-74 qmail: 1302795041.696989 status: local 0/10 remote 0/20
Just so you know, I've hidden the email address on this cut and paste as I don't really want to give that out! but it is a valid mail address!

I was under the impression that Plesk automatically configured and set up mail on installation?

2: Like a dope I installed the 'typical' installation rather than the complete one, how does one go about adding the modules? (I really pray that isn't a reinstall, not really an option as something is going live in a few hours!) (like server health, I forgot to install that)

3: Wordpress - I thought I'd try this out on a test domain I set up and sure enough wordpress has massive issues , as does joomla etc. Script creation, file uploading, even the age old 'asking for ftp' information again (even hard coding it doesn't seem to help), tried sexy bookmarks etc and got a lot of write error issues...... the only way I could get wordpress to run 'right' was the chown the entire directory recursively as root:root. I had a limited amount of success adding the psacln and psasrv to the apache group but I still had errors.

I cannot use sitebuilder, I'm not licensed for it, plus people like to install their own. Using CHOWN everytime I get a customer isn't really an option... Is there something I'm missing here?

4: Connecting to external SQL databases doesn't seem to work, my plesk servers IP is 109.73.99.99 and the IP address of the other server is 109.168.99.99 and has the external ports set up for remote SQL. Whenever I try to add the server to Plesk, it seems that Plesk tries to authenticate using it's IP for the username, rather than the one on the other machine, and it fails, with the following error message
'root'@'109.73.99.99' (using password: YES)

Is it supposed to be trying to authenticate with username@pleskserverip rather than username@remotesqlserverip ?

(just so you know, IP addresses changed for security)

Other than these things, I'm quite enjoying plesk so far and if I'm able to get these sorted out, I'll probably be looking at upgrading my licence.

Any help, is very, very much appreciated!
 
Last edited by a moderator:
Just to add, I've done a clean reinstall of this now with zero change whatsoever, even configured a customer on there, with no success... any help at all on the mail issue alone will be very much appreciated!
 
Ok, some more information for you,

I ran the following, /var/qmail/bin/qmail-showctl

And got the following

qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 1000.
subdirectory split: 23.
user ids: 2021, 2020, 2022, 0, 2023, 2520, 2521, 2522.
group ids: 2020, 2520.

badmailfrom: (Default.) Any MAIL FROM is allowed.

bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.

bouncehost: (Default.) Bounce host name is h109-73-74-74.host.redstation.co.uk.

concurrencylocal: (Default.) Local concurrency is 10.

concurrencyremote: (Default.) Remote concurrency is 20.

databytes: SMTP DATA limit is 12328960 bytes.

defaultdomain: (Default.) Default domain name is h109-73-74-74.host.redstation.co.uk.

defaulthost: (Default.) Default host name is h109-73-74-74.host.redstation.co.uk.

doublebouncehost: (Default.) 2B recipient host: h109-73-74-74.host.redstation.co.uk.

doublebounceto: (Default.) 2B recipient user: postmaster.

envnoathost: (Default.) Presumed domain name is h109-73-74-74.host.redstation.co.uk.

helohost: (Default.) SMTP client HELO host name is h109-73-74-74.host.redstation.co.uk.

idhost: (Default.) Message-ID host name is h109-73-74-74.host.redstation.co.uk.

localiphost: (Default.) Local IP address becomes h109-73-74-74.host.redstation.co.uk.

locals:
Messages for localhost are delivered locally.
Messages for localhost.localdomain are delivered locally.
Messages for h109-73-74-74.host.redstation.co.uk are delivered locally.

me: My name is h109-73-74-74.host.redstation.co.uk.

percenthack: (Default.) The percent hack is not allowed.

plusdomain: (Default.) Plus domain name is h109-73-74-74.host.redstation.co.uk.

qmqpservers: (Default.) No QMQP servers.

queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.

rcpthosts:
SMTP clients may send messages to recipients at h109-73-74-74.host.redstation.co.uk.
SMTP clients may send messages to recipients at h109-73-74-74.host.redstation.co.uk.
SMTP clients may send messages to recipients at diffcon.co.uk.
SMTP clients may send messages to recipients at diffcon.info.
SMTP clients may send messages to recipients at titan.thelongmile.net.

morercpthosts: (Default.) No effect.

morercpthosts.cdb: (Default.) No effect.

smtpgreeting: (Default.) SMTP greeting: 220 h109-73-74-74.host.redstation.co.uk.

smtproutes: (Default.) No artificial SMTP routes.

timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds.

timeoutremote: (Default.) SMTP client data timeout is 1200 seconds.

timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds.

virtualdomains:
Virtual domain: diffcon.co.uk:1
Virtual domain: diffcon.info:2
Virtual domain: titan.thelongmile.net:3

servercert.pem: I have no idea what this file does.

rejectnonexist: I have no idea what this file does.

rsa512.pem: I have no idea what this file does.

clientcert.pem: I have no idea what this file does.

defaultdelivery: I have no idea what this file does.

smtpplugins: I have no idea what this file does.

dhparam512.pem: I have no idea what this file does.

dhparam1024.pem: I have no idea what this file does.

So, some more information for mail!

Hopefully this is going to benefit someone for me finally getting a response!
 
Interesting, I don't have any SSL certificates... wonder why that is... this is about as vanilla as it gets...
 
Hello, thelongmile.

Seems the client couldn't send the mail to remote server. You can see the following error message in maillog:
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)

It indicates the problems with remote SMTP server. Maybe port 25 is closed by firewall or wrong remote SMTP server.
For example, GoDaddy has SMTP port closed by default and requires to specify their own SMTP gateway.
In this case you should ask provider's support about correct SMTP gateway and edit a config file /var/qmail/control/smtproutes.
 
Hello

Thanks for your response. I own the server, and I am the provider and the network that it's on has no blocked ports at all. I've not had any prompts anywhere on the installation to set up anything, nor have I actually set up an SMTP server, or told it to look elsewhere. This is a plain, Vanilla installation, so I don't see what is going on here.

Can you please advise further?
 
Back
Top