I’m all new to this, and I’ve tried Googling for help to no avail, so I’m going to ask this here. Is there any way to force a SiteWorx login instead of a NodeWorx login when a user goes to http://server-ip:2080/ or http://server-ip:2443/ ?
My clients get a bit confused sometimes because they can’t login only to find out they were logging it at NodeWorx instead of SiteWorx.
There is a rewrite which is default, so it correctly sets the link, but you can change this if you want, and your domain is any domain, ie a client could use their own domain name. This then would also set the domain to their domain, leaving only username and password to complete. However, if it’s nodeworx, domain name not needed.
If you use a billing panel like whmcs or blesta, you can set it to login to siteworx directly from billing panel.
I hope that helps and sorry if I have misunderstood your post
Yes, but what I meant was that if ever a user visits the server’s hostname for some reason, I don’t want them to see NodeWorx, I want them to see SiteWorx. Is that possible?
Sorry, I’m not fully understanding what your trying to achieve
If your server hostname is called say srvhost.com, and someone reference this domain, it will not rewrite to siteworx or nodeworx, just simply display whatever website/page you have set. The client would need to add /siteworx or /nodeworx to the hostname to be forwarded to login page.
I fail to see how a client would access nodeworx unless purposefully by typing domain/nodeworx
Our systems upon a client siteworx creation, emails the client an email detailing username, password and siteworx link. The default siteworx account holding page has the siteworx login URL.
If you mean you want both domain/nodeworx and domain/siteworx to go to the siteworx login page, then that’s possible and easy to do, but how are you going to access the nodeworx login page.
I hope that helps and sorry if I still am not understanding
Sorry, I’m not fully understanding what your trying to achieve
If your server hostname is called say srvhost.com, and someone reference this domain, it will not rewrite to siteworx or nodeworx, just simply display whatever website/page you have set. The client would need to add /siteworx or /nodeworx to the hostname to be forwarded to login page.
I fail to see how a client would access nodeworx unless purposefully by typing domain/nodeworx
Our systems upon a client siteworx creation, emails the client an email detailing username, password and siteworx link. The default siteworx account holding page has the siteworx login URL.
If you mean you want both domain/nodeworx and domain/siteworx to go to the siteworx login page, then that’s possible and easy to do, but how are you going to access the nodeworx login page.
I hope that helps and sorry if I still am not understanding
Many thanks
John[/QUOTE]
Hi.
Basically, put it this way. Say, my server IP Address is 1.2.3.4. If a user goes to http://1.2.3.4/ WITHOUT specifying /nodeworx or /siteworx, they get redirected to /nodeworx automatically. I want it so that they get automatically redirected to /siteworx instead.
I have to say this is not the default rewrite, or should not be.
I tested this on one of our production servers and test servers, and it does not rewrite to nodeworx
Have you made any changes to rewrite rules.
I’ll have to look up where you set the rewrite though, but I’ll post it when I’m back.
Thinking aloud, have set any rewrite in a htaccess file at all
Lastly, from nodeworx you can set the default website to show for IP address reference and also, I find it better to. create the server host name as a siteworx account as well
I have to say this is not the default rewrite, or should not be.
I tested this on one of our production servers and test servers, and it does not rewrite to nodeworx
Have you made any changes to rewrite rules.
I’ll have to look up where you set the rewrite though, but I’ll post it when I’m back.
Thinking aloud, have set any rewrite in a htaccess file at all
Lastly, from nodeworx you can set the default website to show for IP address reference and also, I find it better to. create the server host name as a siteworx account as well
Many thanks
John[/QUOTE]
Thanks. I’ll just try to dig in deep in the config files.