Secondary Domains using same files as Master Domain

NodeWorx General Discussion
1

Hello,

I recently began using Interworx – hopefully this is not too stupid of a question.

I will use site1.com to represent my master domain, and site2 to represent my secondary domain.

In NodeWorx, I set up a SiteWorx account with site1.com. I then logged into that SiteWorx account and created secondary domain (NOT pointer domain) site2.com.

I then FTPed into the server, and was taken to the folder containing site1.com and site2.com. I loaded a test image file test.gif into site2.com’s html folder. www.site2.com/test.gif does not work - file not found. I then delete that file and instead load the file into site1.com’s html folder. Now both www.site1.com/test.gif and www.site2.com/test.gif display the image, even though it is only in site1.com’s html folder.

This does not strike me as the correct behavior, but I am used to other control panel software so perhaps I am not grasping the InterWorx implementation properly.

Any help is appreciated! Thank you!

2

Clarify

Since the forum hyperlinked those URLs – I want to clarify – site1.com and site2.com are not my actual sites – they are placeholders used to illustrate the story.

3

Two Things

OK, two things:

  1. After doing some more research, I guessed that this is a NameVirtualHost issue. So, I edited /etc/httpd/conf.d/namevirtualhost.conf and added the line:

NameVirtualHost <MyIPAddress>:80

Saved that, restarted httpd and voila - site1.com and site2.com now load their own files appropriately.

Why did I have to add this line manually? Is this normal? And will doing this break anything?

  1. I should have probably posted this in the SiteWorx discussion rather than the NodeWorx discussion. Oops!
4

Hi Webdev,

This is not normal - InterWorx should add the namevirtualhost.conf configuration line when it is first installed (and auto detects the IP’s currently on the system) and also when adding new IPs on the IP configuration screen. Did you recall how this IP was added?

5

This should have been automatic. I’m going to try to trigger this error on a box running CentOS 6. Was this a fresh install? Have you upgraded recently?

6

hi, i am actually experiencing this problem now. am using 4.10.1 interworx

7

how can i resolve this problem?