Bubka3 Posted June 25, 2011 Share Posted June 25, 2011 In IIS you can bind a website to an domain and use the IP for as many sites as you please. We should be able to bind V2 webserver to a domain. Link to comment Share on other sites More sharing options...
frbnet Posted July 28, 2011 Share Posted July 28, 2011 if you disable IIS and setup V2 Master to use port 80 instead off 8880 it works with like http://cp.redspeedservers.com = your V2 IP in dns setup Link to comment Share on other sites More sharing options...
cyberonfire Posted August 5, 2011 Share Posted August 5, 2011 I dont see why it isnt like it is in TCAdmin 1.0 there its using IIS Link to comment Share on other sites More sharing options...
frbnet Posted August 15, 2011 Share Posted August 15, 2011 think because v2 supports Windows Vista and 7, which has limitations in IIS in numbers of connections Link to comment Share on other sites More sharing options...
ECF Posted August 15, 2011 Share Posted August 15, 2011 It is because V2 allows you to run the master website on linux or windows. Link to comment Share on other sites More sharing options...
Gatsu Posted August 18, 2011 Share Posted August 18, 2011 Linux is able to also handle port 80 The fact that we still can't use a control port that is at the domains/subdomain's root level (cp.domain.com instead of cp.domain.com:8880/Interface/Base/Login.aspx) is odd for this day and age. Also it is now on port 8880. This just adds to the confusion of some users when they want to remember a URL. Link to comment Share on other sites More sharing options...
frbnet Posted August 18, 2011 Share Posted August 18, 2011 insert a default.htm into your cp.domain.com with <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Untitled Document</title> <META HTTP-EQUIV="refresh" content="0;URL=http://cp.yourdomain.dk:tcadminport"> </head> <body> </body> </html> Link to comment Share on other sites More sharing options...
Gatsu Posted August 18, 2011 Share Posted August 18, 2011 (edited) That is besides the point and a bit useless because you can to it better with ip tables. We are trying to find out why it would not be on port 80 and in the root when it is simple to do this in most environments? Edit: we worded this wrong. It is meant to convey that we did have the understanding of port 80 but not the root domain. Edited August 19, 2011 by Gatsu clarification Link to comment Share on other sites More sharing options...
icekohl Posted August 19, 2011 Share Posted August 19, 2011 It's not on port 80 because it's still in beta. Link to comment Share on other sites More sharing options...
Gatsu Posted August 19, 2011 Share Posted August 19, 2011 It's not on port 80 because it's still in beta. This is also incorrect. It is set this way because the normal user that is created (tcadmin) cannot have any ports opened that are below 1024 or something close to that. Our main point is the the fact that it has to be yourdomain.com/interface/default/login.aspx when it should be yourdomain.com There are many reasons for this and not just because it looks better. For example currently if the user is somehow directed to just yourdomain.com/interface or yourdomain.com/interface/default it will redirect you to the loging page but with a call back url in the address bar. Once you log in you receive server errors. Being hotsers and sys admins we all know that is is simply a matter of going back to the original url, and you will have appeared logged in, but for the ignorant masses out there some of them will see that 500 error and simply conclude that your company is bad because the CP is broken. When in fact it was never your fault at all. That is just one example of why it is much better to have the root (domain.com) instead of how it is (domain.com/interface/default/login.aspx) Link to comment Share on other sites More sharing options...
icekohl Posted August 19, 2011 Share Posted August 19, 2011 my bad, misunderstood what you were asking. Link to comment Share on other sites More sharing options...
LFA Posted August 19, 2011 Share Posted August 19, 2011 Getting errors when viewing /Interface/ and other folders is easy to fix. The folder just doesn't have a default document. I will add them in the next update. You can configure the website to use port 80 with iptables: http://help.tcadmin.com/Frequently_Asked_Questions#Configure_the_website_on_port_80 or edit tcadmin-config to run the website as root and you can set port 80 there. This is not recommended for obvious reasons. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now