Apache serving wrong vhost

Discussion in 'Installation/Configuration' started by Th0m, Nov 13, 2020.

  1. TonyG

    TonyG Active Member

    @ahrasis You're frequently much too quick to critize and dismiss. This was not a hijaack, I was providing an example of a scenario that controllably reproduces the symptoms that Thom describes. I use WordPress extensively and found what I thought was the same issue before installing it in the sites alphabetically around the problem site and with no other apparent cache issues. @Th0m said "Seems like the logged in WP user was coincidence." A linked similar issue was resolved with a reboot. I said I rebooted and can still reproduce the issue. I am not crossing HTTP/HTTPS. And this is not a custom-conf. I am using the software as designed using fields providing in configuration screens and according to the documentation. This allows me to confirm the existing docs and to make notes for new ones.

    I gladly accept that the two issues that I relate are not the same as Thom's: incorrect document root and cross-site execution. I also gladly accept when I have made errors. Nevertheless I am having these issues in a default environment. I have verified a defect in docroot assignment, and I offered this information about apache serving the wrong vhost in a thread that the OP titled "apache serving the wrong vhost".

    Really! Leave the attitude at the door.
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    @TonyG : What Ahrasis wrote is correct, in that the problem you describe is not related to the problem @Th0m has in this thread. It may not be obvious the problems are different, but still the situation you described should not be in this thread. Besides, the problem you describe is discussed about weekly in this forum.
  3. TonyG

    TonyG Active Member

    Thanks @Taleman - I've noticed that issue has been discussed frequently and due to the volume thought there was a general trend. I will look more closely at the other threads - only so much time for all of us. My only objection here to the dismissive attitude. Otherwise we're all on the same page. I will do my homework and certainly always try to keep posts pertinent and properly researched.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    This can be achieved by unticking the checkbox "HTTP NameVirtualHost" in the IP settings here: System > Server IP.
  5. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    I know :) But as a lot of users make a mistake, maybe we should add a warning message or something like that.
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Maybe we should add the IP addresses there without HTTP NameVirtualHost enabled at install time?

    -- update --

    Just had a look at the code, we'll just have to change line 496 in installer_base.lib.php from:



    ahrasis likes this.
  7. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Yes, that's a good idea. Will open a issue for it on GitLab.
    till likes this.
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    I've just updated my post with the line that needs to be changed.
  9. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Shall I open a MR? ;)
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Sure, would be a good addition in my opinion :) I guess most users will never have to select an IP instead of * and it will probably prevent many support posts.
    Th0m likes this.
  11. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    @Taleman, thanks a lot. I really appreciate your words.

    Anyone can read that I didn't criticize or dismiss @TonyG summarily but I simply believed his problems and answers are different in my point of view; and I did try provide answers for him as well as for @cremos following after him, which IMHO should be in different threads, but doesn't really matter now.

    I did also note in his post about seemingly recurring problem is the LE broken renewal config for a domain where I did recently response to one in a similar problem before in other thread but I am not sure how did this happen (since previously we did have this problem with certbot on this but was later resolved).

    Hopefully, the LE FAQ help and it won't occur again or we might need to revisit to see what is the real cause.

Share This Page