All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Networking question
I'm not going to let myself be ashamed to admit that I don't know something so here goes.
A situation I've never really encountered here. I've got a domain pointing to my local IP provided by my ISP. The firewall is sending external traffic from the valid ports to a server on the internal network (http, https, apple push services). I have a local OwnCloud VM set to a static IP internally, recognized by the firewall of course, and I want to route external traffic to it.
My question is this. Is there a creative way to redirect a subdomain via an average firewall (SonicWall, nothing fancy) or would I be best to change the apache port on that VM and just force users to use a non-standard port in the URL to access it from the outside? Changing the port seems obvious but I'm wondering if perhaps I'm skipping over a simple way to keep it simple and easy to remember for the end user.
Comments
Most 'standard' firewall implementations aren't at the level needed to determine subdomains. Changing ports would work best.
Apache can forward traffic for some domain/subdomain proxy-pass.
That is assuming port 80 is sent to an apache server and this is why you need another one. Other http servers might do similar things.
However, I still think changing ports is the trouble-free way
Now there's an idea...altering Apple's implementation of Apache actually sounds pretty fun
The firewall will probably only care about the destination ip.
What you need to do is to forward port 80 (http) to a reverse proxy who then translates (depending on the domain) to the correct internal ip.
I had this solution at home once when I needed port 80 to two different servers on the inside.
Squid can do this, and with some extra work also handle https.
This is proving to be quite fun with OS X server. Apple has a strange yet interesting style of implementation that I've not seen before. Example: https://discussions.apple.com/thread/4220124?start=0&tstart=0
This is actually quite a challenge. Could be done easier by going to the OwnCloud VM first and setting up proxy to direct necessary traffic to the Mac server instead of the other way around, but now I'm enjoying this challenge...
Good luck, dont forget to write down the steps for next time.
This reminds me of someone I know which needs to reinvent the wheel each time
I mean anyone can do it the right way, some of us seem to have an obsession with making things work the wrong way :P
Thinking out of the box might bring interesting ideas, you may never know what's after the corner
So if any of you guys ever think it'd be fun to take on the task of altering Apple's configuration of Apache with OS X Server (at least with 10.8), do yourself a favor and don't. Went the other way, direct to OwnCloud server and then proxy to push other traffic back to the Mac server. Didn't have to bother push services since they use their own ports, thankfully.
It isn't that altering Apache configuration is difficult, or that Apple's implementation is difficult. It's actually very well organized and a bit refreshing in how unique it is. Their server application, however, does not take kindly to the slightest change and will refuse to allow services to start for no apparent reason. I mean honestly, how does enabling virtual hosts in httpd.conf cause a ruby error? I don't even want to know.