Posts by medienlampe

Du könntest die Installation auch in einer screen-Instanz laufen lassen, dann kannst Du das entsprechende Fenster einfach wieder an deine neue SSH-Session attachen.
Ansonsten hättest Du notfalls auch einfach den Prozess abschießen können.

Shortly; yes. Technical somemail@gmail.com MIGHT receive your message.
If somebody, let's say sender@sendingserver.com, is sending a mail to e.g. receiver@somedomain.com, sendingserver.com will lookup the MX-Record in the DNS-Entry of somedomain.com to get the corresponding IP address to be able to send the message.
So, if your DNS is configured wrong you won't be able to receive messages because nobody can figure out the correct IP of your mailserver. But you will be able to send messages to foreign addresses as long as they have correct DNS settings.
Nevertheless there is a chance that the foreign mailserver rejects your message when the IP you're sending from and that in your MX record are different. That's because the foreign server cannot verify that you're the legit source of the message (SPAM-/Phishing-Protection).

That error bugs me too.
But it seems to be caused by SpamAssassin itself:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7302

As far as I understand, there is an error in the recent ruleset, causing sa-update to fail with

So, maybe we just have to wait until that has been fixed.

Thanks Nuxwin - I'll close this issue.
Have a nice weekend!

Thank you.

Next week, I'll have a look at it. Would be nice if it would be possible to realize with IP dual stack.

Now that's really, really strange.
I already cleared all browser caches and tried it in different browsers.

What's even more strange is, that it's still showing me the default page on my phone (where I never visited the page).
Well, I now deactivated my WiFi and tried it via the mobile network and it works.

I never encountered something like that before - thank you both very much for your support!

Well, it didn't work at all.
Now, the default Apache2 page is back online.

EDIT:
To clarify: it's just the base-url which isn't working - the other vHosts are running just fine.

Thanks for your answers!

Quote from mrpink

After the upgrade to Debian Jessie did you run the imscp installer again?

If not, please do that: perl imscp-autoinstall -d

Yes, I did that to install my migrated data. The Debian 8 has been installed on a fresh KVM and the old data has been migrated.

Quote from Ninos

Also you could try to purge apache2 and rerun the installer..

I'll give that a try and tell if it worked.

Hi there,

yesterday I upgraded to Debian 8 and installed iMSCP 1.2.11.
Now i've got the issue, that Apache2 is serving the content of /var/www/html on my default server-address via port 80 (thor.medienlampe.de).
I already tried to find the responsible config file via grep -rnw '/etc/' -e 'www/html', grep -rnw '/var/' -e 'www/html' and even grep -rnw '/' -e 'www/html' with no helpful results.

Furthermore, there is no symlink to any default inside sites-enabled for /etc/apache2 or /etc/nginx - I also removed 000-default/default from both sites-available folders.

Thanks in advance for your support!

@Nuxwin that's correct.
Thanks for the clarifying annotations! I'll simply be waiting for the next release.