Posts by tracer

Just use a symlink (symbolic link).

If you are not as lazy as me you can for sure stop mail service before the move and restart them afterwards.

You don't use https?

You, those links are shown where? And after you refresh the site, the links change?

Quote from lestatminiyo

Sometimes we receive a 404 error when navigate throught mailman. Ctrl+F5 fixit temporaly.

Disclosing the URL which can't be found might be helpful …

What is PHP max_execution_time?

PHP max_input_time?

Did you try raising the values?

Are there any recommendations from WP?

Quote from Nuxwin

My answer goes to crafter, not you... I don't really understand the purpose of your answer... If you have been also affected by this bug, you must note that it has been fixed in latest build.

You mentioned me with that @ sign, so I got a notification, was irritated

Quote from Nuxwin

I hate losing my time Why do you try to install an older release exactly?

Oh, I'm surprised, didn't answer, was just a draft, but I didn't remember how I fixed the issue as I tried many things.

I took the last working version. I had severe issues with my underlying Dom0, so I had to get up running more machines. The latest released stopped installing with an error I don't remember right now, but 1.5.3 did, so I left it that way, as there were other services offline, too. For the moment I was happy to have the service back online.

Did you try

as root?

Quote from web4you

imap.web4you-gmbh.ch und smtp.web4you-gmbh.ch

Wo siehst Du dann den Zusammenhang zum i-MSCP?

Ich würde beim provider nachfragen, erwarte aber nicht zu viel Expertise. Wer seine Seite schon mit WP aufsetzt …

Edit: So, wie es aussieht, reagiert er via IMAp gar nicht mit SSL, via SMTP liefert er ein Cert für web4you-server-02.web4you-gmbh.ch aus.

Wenn Du das einträgst sollte senden via SMTP gehen, aber ist ganz sicher nicht im Sinne des Erfinders.

It's not directly related to the plugins, your setup is broken.

Try:

If that gains no result try "apt upgrade", it should tell you which package is broken.

Quote from jackstone

Apparently, after the upgrade the plugin PanelRedirect was no longer installed for some reason, after the (re)install of the plugin, the panel now works on :443

Well, I asked twice for apache2ctl -S. (not -2, my fault …)

With PanelRedict it shows:

BTW, before an upgrade you should disable all plugins and enable them afterwards.