i think you need to edit the resseller there you have the php settings 3x
i changed them to
1003
1002
999
These settings work for me
Now the resseller can add a client and there is also the php setting
i changed them to
1003
1002
999
Done that now the user can use those settings.
ofcourse you can give other vallues
never mind found it
i-MSCP frontEnd (imscp_panel service)
https://github.com/i-MSCP/imsc…errata.md#listening-portsListening ports
The listening ports for the i-MSCP frontEnd were changed to make them compatible with CloudFlare. The new ports are:
I upgraded the 1.3.0 to 1.3.1 all went well sites are ok but admin pannel is no longer reachable did i miss something ?
debian jessie
imscp 1.30 >> 1.3.1
As we said many times, this is a completely different issue. You need to install the correct certificates, which you didn't do yet.
By the way: All server providers I had in the past time answered emails within 1-2 hours.
tell ziggo that
called them twice today and finally got the answer that the person who takes care of that is sick
there is one more but he comes tommorrow
pffff ziggo is no small provider they should have this fxt in no time
I have no certificate but like i said it should work with the shared one
so what is the reason to buy a certificate i dont understand that point
if it makes the mail server better in receiving and sending/comunicating then its something i should considder
and is it possible to make a account on imscp with the fqdn and then let letsencrypt create the cert ?
hopefully tomorrow the ptr/fqdn/reverse dns is ready 
by the way i have no server provider i have my own servers on my own ip's
200mb down 100mb up 5 ip numbers
Could this be caused by the fact that my Fqdn is not ready yet ?
The request for a ptr was made and should be ready tomorrow.
The server is already installed with that Fqdn adres
thats why i asked this im my second post 
Which error exactly. You should provide us the full (exact) error message.
Test-e-mailbericht verzenden: De reactie van de server was: 504 5.5.2 <mijn>: Helo command
this is the error i get when i use the serv2.dummy.nl
incoming mail = mail.serv2.dummy.nl
outgoing mail = mail.serv2.dummy.nl
Why it's strange that lets encrypt is not creating a cert for postfix?
Thats not what i am saying and i understand that its not created for postfix
Thats why i am puzzeled that outlook is using that cert
Display MoreIf you want continue to receive help from us, you should refrain a bit
You're confusing many things here.
The SSL certificates generated by the i-MSCP LetsEncrypt plugin have nothing to do with the SSL certificate used by the mail services (postfix, dovecot, courier...).
The SSL certificate for the mail services is generated independantly during the i-MSCP installation or its reconfiguration. Currently, there is only one shared SSL certificate for the following services:
- Postfix (SMTP),
- Dovecot or Courier (IMAP, POP)
- ProFTPD or vsftpd (FTP)
You can reconfigure that SSL certificate by running the following command:
then you'll be asked for your SSL certificate. If you choose the self-signed option, your mail client will say that the certificate is not valid. If you choose your own SSL certificate, you must be sure that the common name matches your server hostname (hostname -f). Also, when you will setup your mail client, you must use the same hostname.
I dont need a seperate certificate for postfix as i understand it should work fine with the shared SSL certificate
I can use the fqdn for outlook because i have the domain with wildcards so i can use dummy.nl with wildcard serv2 what will result in serv1.dummy.nl
If i use that for outlook then i have another error wich is the helo
etc/hostname is:
serv2
etc/ host is:
213.xxx.xxx.18 serv2.dummy.nl serv2
::ffff:213.xxx.xxx.18 serv2.dummy.nl serv2
hostname -f is : serv2.dummy.nl
So what i am thinking is when the reverse dns/ptr/fqdn is ready that it should work
Its only crappy that i have to make this request for the ptr/reverse dns/fqdn at the isp and that takes time before its done.
@Nuxwin
If you want continue to receive help from us, you should refrain a bit 
You're confusing many things here.
I understand here we say Babelonian speech confusion
We all speak differant languages and english is not our native language so its hard to explain but also hard to understand.
Then given the fact that its not my cup of tea but all hobby for me its even harder to understand. For you guys its all very simple because its your thing and you study for it. But give me a hammer and a screwdriver and i will build you a house thats my thing.
And dont get me wrong i really respect the things you guys do and the magic you create with your fingertips is amazing and i would really love to get your work working for me aswell and i know it should otherwise you would not have created it and there are many who have it working 110%.
My other server works 110% with another pannel but there is litle developement there so thats why i am switching now
I know Lets encrypt does not create a cert for postfix thats why its so strange.
I think the best thing is to wait for my ptr records to be finished by my isp
Just to be clear the server is already installed with the fqdn
Debian ask for this when you install it and i already gave the fqdn during the install of Debain Jessie.
At the moment the mail receive is not working correct .
ok so who is using what ?Postfix? imscp? letsencrypt? my neighbour? outlook?
It does not matter
The fact is when i add an email account it starts with the error that it is using the wrong certificate
I did not add anything with that command line you gave me should i ?
My Fqdn is not yet ready hopefully tomorrow
So how can i resolve this ?
Wait for the fqdn to be ready and install all new?
Edit some files maybe ?
Or is it just me that imagining things and the error that comes up is a mirrage ?
Nope the fqdn is not ready yet so that will not work i use the domain name always did on my other servers also
But i dont understand why postfix is taking the certs from another site
In the main.cf is
smtpd_tls_cert_file = /etc/imscp/imscp_services.pem
smtpd_tls_key_file = /etc/imscp/imscp_services.pem
so it should be using those files ?