Domain Is Pointing to Other Domain When Using Wildcard Instead of Using IPv4

Discussion in 'Installation/Configuration' started by jaypabs, Jul 5, 2022.

  1. jaypabs

    jaypabs Member

    I was currently using a specific IP Address under IPv4-Address in Web Domain settings. However, due to adding of slave server, the IP address in "listen" directive in vhost file in slave server is left blank giving it an error in nginx no host.

    The error is:
    Code:
    no host in ":80" of the "listen" directive in /etc/nginx/sites-enabled/100-example.com.vhost:2
    To fix this issue, I need to remove the IP address in the master server so the listen directive on both server will become:
    upload_2022-7-5_10-22-41.png
    Code:
    listen *:80;
    This work fine on slave server. However, in the master server, when I open example.com, it points to a different website like domain.com. And not on its own domain which is example.com.

    I tested this locally on my computer by also adding multiple IP Address and it works fine. But not on my live server:
    upload_2022-7-5_10-26-16.png

    Can please tell me what I'm missing?

    Thank you
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

  3. jaypabs

    jaypabs Member

    Domain B is also on https. But still, it redirects to another domain. Any other information to check to verify where I did wrong?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    I've explained it in your other post. You must select * for all sites in the IPv4 field.
     
  5. jaypabs

    jaypabs Member

    So it means I can't use * for other site while I use specific IP on other site?

    Edit: I just read your other post. Thanks. I'll update all site to use * instead of specific IPs.
     

Share This Page