Publishing via OSX Server 104

I am trying to set up a client s OS X Server web server to accept their iCal calendars. I have gone through the Apple instructions - create a realm, create a folder, user lists, turn on WebDAV, restart the web server. However, I keep getting an error - Cannot create ical at http://192.168.1.50/iCal.
My question is what does it mean, www user has write permissions to the root document and how do I change that?
Should I enable DNS and create an entry called myserver.com and bind it to the internal IP?
Is there anything else I need to do?
Thanks for your help.
Tom

When you publish to a folder from iWeb what you will get is a Site folder and a separate index.html file. Whatever you named your site within iWeb will then be the name of your Site folder - so if you called your site Site or S, then your site folder will then be called Site or S. Your site folder contains all the relevant html and CSS documents that you need for your site - so if you have a Welcome page then you will see a page that has Welcome.html, plus another folder that has Welcome_files. This contains all the CSS info - this being what your pages look like.
If using iWeb 08 you would publish to a folder and then use an ftp programme such as Cyberduck/Fetch to upload both your Site folder and separate index.html file to your server - these are placed in whatever folder your host has designated for you, mostly public_html. This means that your url is http://www.domain.com/sitename/pagename, but it does mean that RSS feed will work if you need it to.
The other way of doing this is by publishing to a folder and then using Cyberduck to upload just the contents of your Site folder rather than the whole folder itself. This means that your url will then be http://www.domain.com/pagename, but your RSS feed will not work like this.
If you are using iWeb 09, then for the built in ftp, what you need to do is place public_html into the directory/pathway setting and this should work. This should then upload the whole of your Site folder to your public_html folder on your host.
If you just want the contents of your Site folder and not the whole folder itself, then what you can try is to name your website within iWeb public_html and then place public_html in the directory/path and then if your sitename in iWeb is the same as your host/server folder then just the contents will be uploaded to your host and not the whole site folder - then your url will be http://www.domain.com/pagename.
It is not really that complex when you break it down.

Similar Messages

  • Is there a plain English guide to sharing iCal Calendars via OSX Server Mountain Lion?

    Is there a plain English guide to sharing iCal Calendars via OSX Server Mountain Lion? The present documentation is very limited and of no assistance to a beginner like me.

    I don't have a domain set up on OSXServer  I just have server.myserver.private. I have no mail services at server.myserver.private. I uses [email protected] (a different server)  as the email address in the setup process.
    When I go to share the calendar it requires a valid email address, rather than [email protected], so I enter my email address as a test, I try many other email addresses too but the server responds with an error stating " (email adress) was not recognized by the server.  A new invitation has not been sent.

  • How can local user send message to other user via OSX server in mac maverick

    I just install OS X server in mac mavericks and enable services such as message, DNS, VPN, etc. I also create local users and local network users. I add some local users from OSX server to Message app in order to message to server, but I cannot send any message to those user, even Bonjour is available but I cannot use it to send message in local network.
    I already followed all Server Help in Messages like in this image:
    I try to access to my local OS X server via IP address by using other PC, Mac and iPhone and I can get this interface:
    I already try in iPhone to send message to local user in OS X server after accessing to OS X server via IP Address, but I don't know how local user can get that message and I see nothing in message_archives of message data of server. Therefore, how each user in OSX server can message to each other across OSX server ? Does Admin have to write some codes or make configuration for providing message services to those users ?
    Message was edited by: chhanmalin

    Client users need to use XMPP client app to log in to server with account name like in server , then user can send message to other users in server. Client users can use iphone, pc, or mac.

  • IChat LAN-LAN bonjour connection via OSX-Server and Draytek routers ?

    We want to configure a LAN-LAN iChat intranet connection via our OSX-Server and several Draytek 2600 routers. We have static IP-addresses in all local LANs, do LAN-connection via DynDNS and opened the iChat NAT-Ports on every router as described in several posts.
    LAN-LAN connection (e.g. volume mounting and ARD (Apple Remote Desktop)) works fine. We started iChat on every Mac and chatting via .mac accounts also works, but not via Bonjour. The logged-in users are not listed in the iChat bonjour contact list.
    What do we have to configure more ? Starting the iChat service on the OSX-Server ?
    Thanks in advance for help
    Alex
    PowerPC G5 DP 1.8MHz   Mac OS X (10.4.9)   1GB RAM 22 Display
    PowerPC G5 DP 1.8MHz   Mac OS X (10.4.6)   1GB RAM 22 Display
    PowerPC G5 DP 1.8MHz   Mac OS X (10.4.6)   1GB RAM 22 Display

    Bonjour works without a server but will only work within the same subnet. It's likely your routers are on different subnets and so using Bonjour you would only be able to see contacts on the same subnet.
    If you're not seeing anybody else at all, even those on the same subnet as you, then perhaps your firewall hasn't been opened to the iChat Bonjour ports (TCP, 5297 and 5298). There's also an entry for it in each Mac's Firewall config pane.
    You best bet may be to run an XMPP server. iChat server is an XMPP/Jabber server (using a copy of the pretty old Jabberd 1.4 code), but you might want to consider running the superior OpenFire (http://www.igniterealtime.org/projects/openfire/index.jsp) on your server instead.
    Just create all the users on the server and then enter the relevant details into each copy of iChat.

  • Accessing an External HD via OSX Server

    Hi
    I've got a brand spanking mac mini running OSX Server 10.5 for a small (3 people) office
    and I've attached an external HD to bump up the HD space but cannot figure out how to
    remotely access it! Every time we connect we find the shared drives as usual but nothing else
    and I've gone through all the help files and forum but to no avail!
    So can I access this drive and if so how, also can I move the shared mounted folders to the external as we want to keep the MacMini HD clean and just target the external for all work/access
    Any help would be appreciated as this is driving me mad (amongst other things!)
    Thanks

    You use Server Admin to create shares - define which directories on disk are shared and via which protocol(s).
    In Server Admin, connect to your server then click the File Sharing icon in the toolbar. Now click the 'Browse' button and select a drive/directory to share. Use the options at the bottom of the pane to set the sharepoint rules.
    The confusion is likely to be that File Sharing defaults to showing the list of currently defined sharepoints and it isn't obvious that you have to switch to Browse in order to see other directories to share (are you listening Apple Server UI team? )

  • Sometimes get error "looking for something on MobileMe?" after publishing via ftp server

    I published a website I created on iWeb via an ftp server.  Sometimes it works, but sometimes I get the error "Looking for something on MobileMe?"  My web host says all my settings are correct, so the problem is likely to be in iWeb.  How can I fix this?

    I use FatCow as both my domain registrar and my web host, a similar service to GoDaddy.  The FatCow tech support said all my settings were correct.  Here's a pic of the iWeb Site Publishing Settings page:
    When I try "Test Connection," it succeeds.
    I originally published using MobileMe, then switched to ftp using FatCow.  The ftp publishing worked at first, then I started getting the error message intermittently, now get it all the time.  The FatCow tech thought that something is likely to be imbedded in the code that is taking it to MobileMe.
    Thanks again for your help!

  • Publishing via FTP server

    I have now shifted my webpages from Mobile Me to a local web hosting service, and need to know how I go about uploading them to this new server in the way that was advised on a recent post: "When you FTP up the files, instead of FTP'ing the index file plus folder it generates, you FTP up only the contents of the "inner" folder (which also includes an index file). This creates the standard URL without repeated words. The whole process is simple - publish iWeb to a folder, FTP contents of inner folder." Please help!

    When you publish to a folder from iWeb what you will get is a Site folder and a separate index.html file. Whatever you named your site within iWeb will then be the name of your Site folder - so if you called your site Site or S, then your site folder will then be called Site or S. Your site folder contains all the relevant html and CSS documents that you need for your site - so if you have a Welcome page then you will see a page that has Welcome.html, plus another folder that has Welcome_files. This contains all the CSS info - this being what your pages look like.
    If using iWeb 08 you would publish to a folder and then use an ftp programme such as Cyberduck/Fetch to upload both your Site folder and separate index.html file to your server - these are placed in whatever folder your host has designated for you, mostly public_html. This means that your url is http://www.domain.com/sitename/pagename, but it does mean that RSS feed will work if you need it to.
    The other way of doing this is by publishing to a folder and then using Cyberduck to upload just the contents of your Site folder rather than the whole folder itself. This means that your url will then be http://www.domain.com/pagename, but your RSS feed will not work like this.
    If you are using iWeb 09, then for the built in ftp, what you need to do is place public_html into the directory/pathway setting and this should work. This should then upload the whole of your Site folder to your public_html folder on your host.
    If you just want the contents of your Site folder and not the whole folder itself, then what you can try is to name your website within iWeb public_html and then place public_html in the directory/path and then if your sitename in iWeb is the same as your host/server folder then just the contents will be uploaded to your host and not the whole site folder - then your url will be http://www.domain.com/pagename.
    It is not really that complex when you break it down.

  • Is it possible to connect my home computer to files stored on my running osx server mac via VPN

    Is it possible to connect my home computer to files stored on my running osx server mac via VPN. I have VPN set up and can access the Calendar and Contacts via a web browser, however I want to be able to access data files store on the hard drive and shared external drives connected to it. The MacPro runs OSX Server Lion. Any Ideas if this is even possible or how to do it!

    Yeah, that's what I kinda figured. Maybe there is another solution - here is my situation:
    I have internet and cable service through Telus. Telus' system consists of a modem/set-top-box that provides internet (ethernet and wifi) and TV signal (corded) for one TV and another set top box that provides internet (ethernet only) and TV signal (corded) for my other TV in the basement.
    I have an Airport Extreme connected to the modem upstairs which I am using as my home network wifi. I also have an external hard drive (USB) connected to it on which my iTunes library is shared with all Apple machines in my home network.
    My upstairs ATV, connected to my APE, works fine and streams internet (Netflix), iTunes Store and my shared iTunes drive just fine - the APE is 3 feet away with a great signal.
    My downstairs ATV, also connected to my APE via wifi, does not stream so well, particularly the media from the shared drive. I suspect that this is the case because of signal degredation.
    Any suggestions on how to reconstruct my home network to enable my downstairs ATV to work properly?

  • No longer seeing Publish to private server after OSX/iCal upgrade

    Hi,
    After Upgrading to OSX Lion and updating Ical, I have come across a problem.
    Excuse me if I do not get all the options and menu options correct, I'm using a dutch version.
    I have been using Ical to publish the calendar of our business to our website for some time now, I publish it to an ftp server where a php script presents the calendar to the visitors. After the upgrade I no longer see the "publish to private server" option under publish. I now only see "share with everyone" and "share with invitees". It has since not been synchronizing. I hope someone knows a solution or can give me directions as to what I'm obviously not seeing.
    Thanks.
    Versions
    iCal : 5.0 (1535)
    OSX: 10.7.1

    Calendars listed under your MobileMe login name (which reside on the MobileMe server) cannot be published to a web page. This facility is still available as before for calendars listed under 'On My Mac'.
    MobileMe calendars can be shared privately to other MobileMe members (read-only or read-and-write); or publicly (read-only) to anyone with a CalDAV client - this includes iCal and Google Calendar (free subscription required for the latter).
    Please see this page for more details:
    http://www.wilmut.webspace.virginmedia.com/notes/sharedcalendar.html

  • OSX Server 10.6.3 - (Multiple) Website hosting via Server Admin

    Has anyone else experienced/had this problem? I am posting this hear in hopes that someone else has experienced this as well and may know how to correct/resolve this problem.
    We currently have purchased a collaboration software I have installed and I am running via OSX. The files are stored in /Library/WebServer/Documents/collab. OSX comes with a default website built in at /Library/WebServer/Documents. I intend to install the collab website in anticipation of adding more sites in the future and possibly utilizing the default OSX web services as well. I have set up our internal DNS server to route collab.company.com to the internal ip address of our OSX server. The default OSX webpage is currently hosted on port 80, I am running our collab site on port 8x (we are already hosting websites on a different server on port 80, and the router can only forward port requests to a single ip address).
    With this configuration, if I enter the address of collab.company.com, I get the default OSX server running on port 80. If I enter collab.company.com/collab, I then get our collab website (on port 8x). Essentially I want collab.company.com to open the collab website, not the OSX website. What is odd is, it seems that if I uncheck the default OSX webpage in server admin and disable it, change the collab site to port 80 as a test and go to collab.company.com I get a failed connection that the site is down or doesn't exist, like it is offline. It seems almost as if OSX is completely shutting down the entire directory of /Library/WebServer/Documents which is where the collab website exits inside of (Documents/collab). If I re-enable the default OSX website, then both websites become live again.
    So I guess my question is, is there a different structure/architecture that should be followed to prevent this behaviour? If so, how do I get multiple websites installed and configured properly in server admin to respond to their appropriate dns requests. I also forgot to mention for my collab site entry in server admin I have the host name in the general tab as collab.company.com, as well as the alias collab.company.com, but when I enter collab.company.com I am getting the default OSX site.

    I agree, this seems to make sense in theory, but here is the result I am getting.
    I have my internal (not my osx server) dns server containing a host entry of collab.company.com = 192.168.1.xx. I have a virtual host entry in OSX in the aliases area (correct?) of collab.company.com for my collab site. However, whenever I enter the url in my browser of collab.company.com, I keep getting the default Mac OSX Server website page. I even put an alias in the OSX server site of mainpage to try and differenciate it, but it doesn't seem to take or matter.
    So once again, in theory I think "oh, just uncheck the enable button next to the default OSX website", I uncheck it, and then both of my websites are offline, or appear to be? For my collab site, the link redirects, but I get the error page.
    Safari:
    Not Found
    The requested URL /collab/public/index.php was not found on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
    Apache/2.2.14 (Unix) PHP/5.3.1 Server at collab.company.com Port 80
    Google Chrome:
    Oops! This link appears to be broken.
    Thing is, I even changed my collab site to be running on port 80 as well as a test. I check enable for my osx default page, and they are both back online. If I change the default osx sites port to say 87 or something, and leave the collab at 80, I then get the same bad request messages etc. If I put the osx site back to port 80, they both work.

  • Configure MacMiniServer 2,53 GHz MAC OSX Server 10.6 via Windows 7 PC

    Hi,
    i have a problem. I bought the MacMiniServer 2,53 GHz MAC OSX Server 10.6 and I want to configure the MacMiniServer via a Windows 7 PC. But the Mac Mini Mac OS x Server Install DVD can not open with a Windows 7 PC. Is there a possibility to start the install DVD from a windows 7 PC. I have at this time only a Windows PC.
    Thanks for your help.

    Hi
    The MacMini Server having no optical drive has nothing to do with what you want to do. The server OS comes pre-installed.
    All you have to do is follow Mr Hoffman's suggestions.
    Any USB Keyboard and mouse will do. Your only problem as far as I can see is finding a suitable monitor and/or DVI adapter to connect it to. It may be worth your while purchasing a Mini Display Port to VGA adapter?
    Tony

  • FTP Access on OSX Server via a browser

    I have a number of ftp clients set up which can succesfully upload/download files using ftp client software (Fetch/Easy FTP).
    I have a windows user who wants to upload his stuff via ftp in his web browser (IE presumably).
    Not had any success (Guest access is disabled) with his account settings in browser though I can get in using same settings in ftp client.
    Is this possible with the built in ftp element of OSX Server without having to install something like Rumpus?

    IE is the only browser I know of that supports FTP upload via the web browser window. Most Mac browsers that I'm aware of simply pass the FTP connection off to the Finder to deal with.
    The Finder, of course, doesn't support FTP upload.
    So unless your clients are comfortable working in the command line, you're going to need some additional software. That software could be as simple as an AppleScript application that performs the upload, but you're going to need something.

  • How we set up multiple websites on OSX Server

    BACKGROUND
    After fiddling and futzing around for weeks (actually since last year) I've finally figured out how to set up multiple websites (virtual sites) using one port and one IP address. While there seems to be lots of discussion on this topic, it seems that the basic assumption is that one knows everything about websites, DNS and all that stuff, which I do not.
    When our network was originally established the engineer set up a wiki and also configured webmail, so we had two sites, one secured for mail and the other open for Calendar and the wiki. We were not hosting any websites locally because our school website is hosted by a company in New England.
    This year I wanted to set up websites for teachers and students. As great as the wiki is, there are some things it just can't do as well as a website. So I figured if I set up the sites teachers could link back and forth from one to the other. In addition kids could now start to use a real website instead of the cobbled together file mess I had when we ran a Windows network. Also iWeb is a much more accessible tool than FrontPage.
    SERVER SIDE:
    Snow Leopard Server - 10.6.4
    There are two - actually three pieces if you want your iWeb clients to connect to the server: Server Side Web Services, DNS and, in my case, FTP.
    ================================================ SERVER SIDE - WEB SERVICES
    If you haven't turned on Web services, you'll need to open Server Admin and do that. If you don't know how to set up web services - just reply and I'll step you through that as well.
    Once web services are set up and turned on, you'll see it listed under your server’s name in the Server Admin sidebar. Click on "Web" and then click on the "Sites" tab at the top of page. This is where you list all your sites.
    Click the plus button and enter the fully qualified name of your site, for example: "students.myschool.org". Don't use the defaults here (no name) - that's what got me in trouble before. BE SPECIFIC!
    You'll be looking at the "General" tab (the other tabs, "Options", "Realms", etc. we'll deal with in a second).
    On the "General Tab", the default IP address ("any") and port (80) is just fine. We'll run everything over port 80. (Apache figures all the virtual site stuff out - you don't need your rocket science degree for that.)
    "Web Folder:" is important because this is how you'll "segment" your websites. While I would NEVER do this again, we have a solid state hard drive for the OS and a RAID array for our data files. IF you have that, make sure you do NOT use the default "Web Folder" because it will store all your files on your solid state drive. There may not be enough room, over time, on that drive. I've not experienced it yet, but it's my understanding that if the drive fills up, the server shuts down.
    I store my web sites on a folder on the RAID array.
    Everything else on that tab can be left as the default. (Just make sure that you have an "index.html" or "index.php" file in your web folder root, but iWeb will take care of that for you.)
    I would put in your email address in the "Administrator Email:" field.
    Under "Options" you really don't have to put anything. I've tested making websites with iWeb and it doesn't appear that anything needs to be checked.
    Nothing needs to be entered in "Realms" as well from what I see working w/ iWeb.
    The defaults in "Logging" are fine.
    You can leave "Security" alone, but we do have a (self-issued) certificate listed for our webmail site.
    "Aliases" is important. Under "Web Server Aliases" you enter how you want the site to respond to when users type in a URL in their web browsers.
    When our web server was initially set up the engineer set up "wiki.myschool.org" on port 80 and "mail.myschool.org" on port 443. In the aliases section was nothing but a "*" (the wildcard character). That means, from what I can figure out, that the webserver will respond to these sites regardless of what is typed in the URL. (Well, something like that - point is, if you create OTHER websites, you'll NEVER get to them because the wildcard character in the "Aliases" section, in effect, grabs those web requests and redirects them to the sites that are already there.
    In my case I deleted both of those wild card characters. For my "wiki.myschool.org" site, I entered "mail.myschool.org". That means if you type EITHER "wiki." or "mail.", go to the site that’s stored in the “Web Folder” we set up when those sites were created.
    For "mail.myschool.org" I just DELETED the wildcard character. I wanted that site (since it was secured) only to respond to "mail." - nothing else. (You're not going to that secured site for any other reason than to get your mail.)
    "Proxy" can be left blank. Have no idea what that does. As time permits I'll do some research and figure out what it's used for.
    "Web Services" is if you want to provide any MORE services to this particular site. Most likely you'll want to uncheck all the boxes. For our "wiki." site, we have checked "Wikis", "Blogs", and "Calendar". For our "mail." site we have those checked PLUS "Mail".
    I would create a separate "Web Folder" for each of your sites. I don't know if that's a requirement but for housekeeping purposes, I would keep the sites separated. And I SUSPECT that it's "best practice" to separate your wiki from your other websites.
    SERVER SIDE - DNS
    OK...now you have to make your site reachable and the only way to do that is to set up DNS so that folks don't need to type in the IP address of your web server. You need to set up DNS inside your network and, if you want folks in the outside world to reach your website, you'll need to set up an external DNS as well. I'm going to cover INTERNAL DNS - if you don't know how to set up EXTERNAL DNS - reply or email me and I'll post those instructions.
    Most likely you have already created Zones for you network...all you really need to do is create "Aliases" so that when you type "students.myschool.org" your web browser will know that site resides on IP address XXX.XXX.XXX.XXX.
    If you've set up Zones then you already have a "Machine" setting that translates your server’s name to an IP address and vice versa.
    All you need to do is create an "Alias" (CNAME) record for, in this case, "students". You’ll see the choices for types of records when you click the "Add Record" button.
    There are only two fields to configure for a record: "Alias Name" - in this case "students" and "Destination" - in this case "servername.myschool.org". (You've already entered a machine record that says "servername" = 192.168.1.x.)
    That's it for Internal DNS.
    SERVER SIDE - FTP
    Now you have to get iWeb to communicate with the webserver.
    There are only three ways iWeb will communicate with webservers: MobileMe, Local Folder and FTP Server.
    Local Folder is really only practical if you want to host a website on a laptop (I was blown away initially when I found out that all Macs had a built-in web server - how neat is that?). I think there are some very cool things teachers could do with configuration, and, of course, you wouldn't need to set up any web services on the web server, but that's for another discussion. You need to set up FTP services on the web server.
    Turn on and enable FTP on your webserver.
    You can leave the defaults for "General", "Messages" and "Logging". "Advanced" is the only thing you want to set. I set "Authenticated Users See:" to "Home Folder Only". I set the "FTP Root" to the same root folder in which I plan to store my web sites (/VOLUMES/RAID Array/WebServer/Documents). This setting sets that folder only to be accessible via FTP.
    I would suggest returning to your DNS settings and adding one more "Alias". Set "ftp." to point to your webserver. Why? So folks can edit their sites from home (see below).
    CAVEAT: If you are running FTP on other servers, make sure that the settings here do not conflict with the settings on the other servers. For example, I'm running FTP on my file server so that my scanners can communicate with it. However, I configure my FTP settings by machine name and NOT "ftp.myschool.org".
    ================================================
    CLIENT SIDE - CONFIGURING iWEB
    Now you have to configure iWeb so that it will communicate with your server.
    Click on the "Site" icon so that "Site Publishing Settings" appears.
    Publishing:
    "Publish to:" = "FTP Server"
    You can set the "Site name:" and "Contact email:" to whatever you want. But see below!
    FTP Server Settings:
    "Server address"=ftp.myschool.org (you could also enter in servername.myschool.org or the IP address. However, if you want folks to be able to work on the site from home, you will need to configure external DNS for that. If you use the IP address, you're out of luck for remote access to the site. (You can do it but it's beyond the scope of this discussion.)
    "Username" & "Password" should be your user's network login credentials.
    "Directory/Path" - this is important. Remember, you set your "FTP Root" to be "/VOLUMES/RAID Array/WebServer/Documents". If you leave this field blank then the website will be dumped into this folder. If you are only setting up one site, that may be OK. However I wanted to set up a "students" site folder, a "faculty" site folder and a separate site for our literary magazine.
    THEREFORE: I have, in my ..../Documents folder (on the server), a "students" folder, a "faculty" folder, and a "litmag" folder.
    SO...in my "Directory/Path:" field, I have "/faculty". That means the full path to this website is "ftp root/faculty" or "/VOLUMES/RAID Array/WebServer/Documents/faculty" (You don't need a trailing "/" character. iWeb will automatically append the folder for you user depending on what you entered in "Site Name:" in the "Publishing" area.
    Website URL:
    This is the root website depending on whether it is "students" or "faculty". Since iWeb will append the site name to this root website, I accomplished what I hoped to accomplish in this post (http://discussions.apple.com/message.jspa?messageID=12288561#12288561).
    Faculty sites will be @ http://faculty.myschool.org/username. Students @ http://students.myschool.org/username. PERFECT!
    iWeb is such a GREAT tool - NOW the kids can start using it!
    I want to reiterate that this works for our school but it should work for you as well. There may be better ways to do this but it works for us.
    Hope this has been helpful and you won't have to spend weeks trying to figure this all out by yourself!

    OK...here's how we did it.
    To get access to the website you created from outside your network there are a couple of steps.
    First, you have to have a STATIC IP address from your ISP. If you have a T1 circuit, no problem...you usually get a couple of static IPs you can use. However, if you have a cable modem circuit, most likely you have a dynamic IP address which changes when you connect to the internet. Usually a static IP will cost a bit more because the ISP has to go through a couple of steps to set it up for you. But once you have the address, you now have a way for folks outside your network to connect with you.
    (I’m also assuming that you use a router of some sort through which traffic flows out to the internet and that you aren’t using connection sharing or something like that.)
    The next thing you need to do is have your new static IP address associated with the server on which you are hosting your website. You've probably already done that if your website works inside your network. However, you've associated a private ip (192.168.x.x, etc.) to your web server. That doesn't mean anything to folks on the outside because private IP addresses are just that - private - folks can't access them. (I won't get into VPN because that's a whole other topic.)
    The way you associate your new static IP address to your web server is through some sort of dns application from your ISP. For example, we use TierraNet to manage our external DNS information. They have a web interface control panel that is very similar to the DNS interface for XServer. You can create CNAME records (aliases - other ways that folks can access your servers).
    Basically you create an "A" (CNAME) record with a fully qualified domain name (e.g. webserver.myschool.org) and point it to your public IP address (XXX.XXX.XXX.XXX) which you just got from your ISP. It's going to take a while (24-48 hours) for this change to take effect. BTW, you can create as many “A” records as you want. For example mail.myschool.com and wiki.myschool.com could point to the same place.
    You want to make sure that the fully qualified domain name you enter in the external dns utility matches the name you used when you created your internal dns records on your XServer.
    OK...so now folks can get to your domain - but, remember, you have a private network IP scheme between them and you. You now have to tell your router that when web traffic arrives, allow it inside the network and direct it to your web server.
    Let's say your public IP address is 205.100.112.50 and your web server is 192.168.0.5.
    You have to create, in your router’s "Security Zone" (router companies call them different things) a couple of rules. Usually the first rule is: "Let everything inside the network get out to the web." You've probably already done that if folks inside the network can reach the internet.
    You then have to tell the router to allow web traffic (port 80) into your network AND redirect that traffic to 192.168.0.5.
    We use AdTran routers and they have a web interface which allows you to write "rules" affecting public and private traffic. Public is folks outside the network, private is folks inside.
    AdTran calls them "Security Zones" and you modify those zones with policies.
    So my "Policy" would say, in the above example, redirect traffic from my public IP (205.100.112.50) -> to my web server -> (192.168.0.5).
    THEN you have to modify this policy with what AdTran calls "Traffic Selectors". You've said, OK, you can get in, but WHAT can get in?
    The "Traffic Selector" is written to say: "Permit" "TCP" traffic from 205.100.112.50 only through Port 80. (That's the port that web traffic goes over. If you wanted a secure website, you'd add another traffic selector that opens port 443, for example.)
    I'll tell you I'm no genius when it comes to this. I called AdTran and had them configure my router for me. I told them what I wanted done, they remoted into the router and configured it. But then I could go to the web interface and see what they did and then added rules later on when I wanted, for example, to get access to the network via Apple Remote Desktop or VPN into the network on my iPad.
    I'd bet that your router has a maintenance agreement that includes this service and if it doesn't it should have.
    I did find that I still had issues when I tried to set this up originally and it had to do with the ORDER of the policies. I can’t remember exactly what the issue was, but, effectively one of the policies highjacked traffic before the policy that I wanted got triggered. Simply moving them around in the list fixed that issue. So if you have this set up but still can’t access the site, check the order of your rules.
    I don’t know if that helps or not, but I try to think about this stuff conceptually and then get someone to help me with the details. I work with this stuff so infrequently that I forgot how I did something 6 months or a year ago. I’m in the process of creating a wiki for the school which documents all this stuff, but that’s a major undertaking.
    Cheers,
    John

  • Using Amazon S3 as linked storage with OSX Server 10.6.7

    Hello everyone!
    I will be getting a nice Mac Mini OSX Server tomorrow. I'm not new to networking and I've done over a month of reading the PDF's here that are related to the server and software. I think it's a great tool at a great price.
    My question is:
    1) Is there a way I can use the S3 Amazon Simple Storage Service as secured linked storage space or SMB to the OS X Server?
    2) Is there a way that the OSX Server software can pass both the S3 Access Key and Secret Key to S3 to securely access directories on the S3 Amazon Cloud?
    I would like to use S3 Amazon Simple Storage as a secured disk space solution that would be reliable a quick. Am I asking too much?
    Thanks!
    JT

    Would it be a good idea to have another computer link to the Amazon S3 then have the OSX Server link through that computer to S3?
    Or would I have to create a script / CGI to authenticate to Amazon S3 to access the directories.
    My goal is to use Amazon S3 as copy and playback storage.Like a hard disk connected to the OSX Server via a firewire or an Ethernet connection. Does the sound too simple? It must be possible.

  • Help needed with OSX Server 10.5.8

    We're running a headless Xserve (RackMac3,1) with OSX Server 10.5.8 that did its job flawlessly.
    Now we want to update the Perl software from 5.8.6 to 5.20.0 or newer. After downloading the suitable version from CPAN we tried to install, but get the following msg:
    Uh-oh, the C compiler 'cc' doesn't seem to be working.
    You need to find a working C compiler.
    Either (purchase and) install the C compiler supplied by your OS vendor,
    or for a free C compiler try http://gcc.gnu.org/
    I cannot continue any further, aborting.
    Is there a way to install the missing tools remotely via the command line (SSH)? A step-by-step recipe would be most welcome.
    - Harald -

    RackMac3,1 is PPC/G5 processor so you are not going to have an easy time with this. Perl 5.2.20 is bleeding edge (OS X 10.10.3 comes with v5.16.3).
    I would leave Apple's installation of Perl, etc. on the server strictly alone and install MacPorts:
         The MacPorts Project -- Home
    and work from there. You aren't likely to get a step-by-step recipe because its not an exercise a rational person would chose to spend time on.
    Have you considered rewriting whatever features in your code require Perl 5.2.20 than to upgrade your server? Or buy a new server, you could probably pick up a Mini for about $200.
    C.

Maybe you are looking for