![]() ![]() You may get a reply saying, "Web service is off." Of course, in order for the server to respond with the "Web service off" message, the Web server has to be on, so OS X Server ends up blocking Rumpus even though it's not really doing anything. Turn off Web service in OS X Server and try to connect from a Web browser. Unfortunately, turning off OS X Server's Web service can be tricky. But if you don't need OS X Server's Web service, the better option is to turn it off so that Rumpus can run on the default Web port, simplifying access and minimizing client firewall problems. In Rumpus, you can specify the Web server port on the "Web Settings" window, "Options" tab, and the secure Web port on the "Network Settings" window, "Secure Services" tab. If you need to run both Rumpus and OS X Server Web services, you can run one service on the primary Web port (80) and another on an alternate (like 8000). The exception to this is port conflicts, when OS X Server and Rumpus try to use the same port for one or more services. Rumpus includes it's own HTTP and FTP server engines which are totally separate from the Web and FTP servers built into the system, so they coexist very well. In general, Rumpus and OS X Server get along great. There is an updated blog post that describes how to handle this issue in OS X Server 5 HERE. The information below relates to OS X Server 4 and earlier. ![]() Important Update! Since this article was originally posted, things have changed. John's Blog: Turning Off OS X Server's HTTP Service ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |