| Author |
Post |
ilconte
Member
milano
Post: 1 |
i can get to the site internally but no access from outside to my sitex
what can i do to give or get access to my sitex site from the outside
other option to use in sitex on sme server
i have forwaded port 80 on the router to sme server
but i have problem
any help greatly appreciated |
|
pmills
Gold Team
Localizers
Beta Tester
Developer
Moderator
Member
Site Admin
Tallinn, Estonia
Post: 1,401 |
Sitex sites cannot have more than one URL
so if your internal address is for example http://192.168.0.1 and thats the address you used to setup SiteX, the site will not function correctly when accessed from the external URL.
If you want sitex to work externally, make a simple html test page at your site URL first, verify that its working when you visit from the external URL, and once you're happy that it is, you can setup SiteX, but when you do, you must use the external URL during setup.
There is no official SiteX support for SME server, but if you search these forums for SME you should be able to make direct contact with the person who is leading that project.
[Edited on 08/19/09 @ 12:51PM]
Fighting fires... and creating a few of my own...
|
|
realbruts
Member
Post: 4 |
Hmmm... that internal address vs. external address resolution sounds like a real problem for SME gateway users like myself! That means I have to steal the WAN connection to set up SiteX, or go off-site...
I've run into this issue, and now I'm wondering how to get myself out of it...
Do I have to uninstall/reinstall sitex? I cannot get to the sitex/login.php externally now - after running it internally.
Is there a way to alter the stored IP information to reference the external address without totally tearing down SiteX?? |
|
pmills
Gold Team
Localizers
Beta Tester
Developer
Moderator
Member
Site Admin
Tallinn, Estonia
Post: 1,401 |
Easy workaround if you're using windows: You can just edit your hosts file to resolve the internal IP to the external name of your site (assuming your site has a domain name).
Fighting fires... and creating a few of my own...
|
|
realbruts
Member
Post: 4 |
I don't think that works - LMHOSTS entry would be the same as using the internal IP address to set up SiteX (which is the problem right now).
If I specify my EXTERNAL address, I talk to the DSL modem - and I can't break that link because occasionally I do need to talk to the DSL modem.
Ignoring that issue for the moment, what's the procedure for unscrambling the SiteX installation? Uninstall/reinstall?? |
|
pmills
Gold Team
Localizers
Beta Tester
Developer
Moderator
Member
Site Admin
Tallinn, Estonia
Post: 1,401 |
There's no reason it shouldn't work
you can make any external domain point to an internal address instead using the hosts file. I don't know about LMhosts.
The other option, most good routers have a setting to resolve external addresses internally. For example in pfsense you can enable/disable NAT reflection, which addresses this issue.
to fix your existing install, using phpmyadmin (assuming its installed with SME) you can just edit the 'URL' key in the SiteX_Setup table in your database
Fighting fires... and creating a few of my own...
|
|
realbruts
Member
Post: 4 |
Thanks for your help.
I jumped the gun and removed everything & re-installed SiteX. Configuring it from the WAN port worked... it's just cumbersome.
My SME server *IS* the router, and I bet there's a way to forward the internal port 80 to the external port 80 - but it eludes me right now...
For the internal access, it knows that my FQDN translates to just the server name, and it happily does that for me every time... before SiteX gets to see it.
I'm up and running - and I'll find a way around the internal access issue. |
|
davidiwharper
Member
Beta Tester
Sydney, Austrailia
Post: 65 |
As per the SME Server wiki (http://wiki.contribs.org/SiteX):
Finally, you must go to the Site Preferences administration panel and set the FQDN from which your site will be accessed, e.g. http://www.mysmedomain.com/sitex. By default, SiteX enters your unqualified servername as the URL, e.g. http://server/sitex, making external resolution by visitors impossible.
[Edited on 06/10/10 @ 11:36AM] |
|
