Newsroom Update

Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Community User
Community User Author

How do you get wiki on HTTPS working?

Hi All,


I have been searching the internet and Apple Discussions,


When I browse to http://mysite.com/wiki it loads the wiki

When I browse to https://mysite.com/wiki it gives error:

Not Found

The requested URL /wiki/ was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


If I browse to https://mysite.com/ it appends /UI on the end of the address with the error above.


I have all the relevant port forwarding/NAT in place hence how it reaches the page. Am I missing a tickbox option or do I have to configure a config file for public access to the wiki via https?


I have the certificates setup and assigned under server admin>websites>server website(SSL)

If I browse to https://mysite.com/ it appends /UI on the end of the address with the error above.


All is fine with HTTP (80), just not HTTPS(443)


Hope someone can help,


Many thanks,

Mac mini, OS X Mavericks (10.9.5), [Mercury] OS X Server

Posted on Jul 24, 2015 7:28 AM

Reply
14 replies
User profile for user: Community User
Community User Author

Jul 24, 2015 8:23 AM in response to Linc Davis

I dont believe any Apache files have been modified. Do you know which one(s) I could check?


Mercury is the name I have given the server.


Many thanks,

Reply
User profile for user: etresoft
etresoft
User level: Level 8
46,318 points

Jul 24, 2015 10:08 AM in response to Community User

Hello ~Luke,

Can you explain your situation a bit more? Is this a public web site you are running from your Mac? I strongly recommend not doing that. There are many fine web hosting providers that will do all of this for you. If there is a problem, which there usually isn't, they will take care of it for you. If there is a zero-day security exploit, which there is every couple of weeks, they will take care of it for you it. If you do need some customization, there is a huge resource of other people running the same software on Linux. When it comes to servers, Linux has passed the Mac a long time ago. OS X Server is useful for a few specific tricks. But if you need to serve a website on the internet, let the professionals handle it with Linux. That's what Apple does.

Reply
User profile for user: Community User
Community User Author

Jul 24, 2015 11:54 PM in response to Community User

Thanks Linc, here it is:
----------------------------

server$ ls -l /Library/Server/Web/Config/apache2

total 224

-rw-r--r-- 1 root wheel 13234 27 May 2014 ReadMe.txt

-rw-r--r-- 1 root wheel 1621 24 Jul 14:52 WebConfigProperties.plist

-rw-r--r-- 1 root wheel 1626 27 May 2014 WebConfigProperties.plist.default

-rwxr-xr-x 1 root wheel 23440 23 Oct 2014 getsslpassphrase

-rw-r--r-- 1 root wheel 485 27 May 2014 httpd_ACSServer.conf

-rw-r--r-- 1 root wheel 395 27 May 2014 httpd_calendarserver.conf

-rw-r--r-- 1 root wheel 100 27 May 2014 httpd_corecollaboration_changepassword.conf

-rw-r--r-- 1 root wheel 2268 23 Oct 2014 httpd_corecollaboration_shared.conf

-rw-r--r-- 1 root wheel 2388 22 Oct 2014 httpd_corecollaboration_shared.conf.prev

-rw-r--r-- 1 root wheel 93 27 May 2014 httpd_corecollaboration_webauth.conf

-rw-r--r-- 1 root wheel 92 27 May 2014 httpd_corecollaboration_webcal.conf

-rw-r--r-- 1 root wheel 170 27 May 2014 httpd_corecollaboration_webcalssl.conf

-rw-r--r-- 1 root wheel 596 27 May 2014 httpd_corecollaboration_wiki.conf

-rw-r--r-- 1 root wheel 3685 23 Oct 2014 httpd_devicemanagement.conf

-rw-r--r-- 1 root wheel 4288 23 Oct 2014 httpd_devicemanagement_ssl.conf

-rw-r--r-- 1 root wheel 399 27 May 2014 httpd_gitweb.conf

-rw-r--r--@ 1 root wheel 22960 24 Jul 15:04 httpd_server_app.conf

-rw-r--r-- 1 root wheel 22969 23 Oct 2014 httpd_server_app.conf.default

-rw-r--r--@ 1 root wheel 22959 24 Jul 14:59 httpd_server_app.conf.prev

-rw-r--r-- 1 root wheel 780 27 May 2014 httpd_webdavsharing.conf

-rw-r--r--@ 1 root wheel 528 24 Jun 2014 httpd_webdavsharing_sharepoints.conf

-rw-r--r-- 1 root wheel 3535 27 May 2014 httpd_webdavsharing_template.conf

-rw-r--r-- 1 root wheel 66 27 May 2014 httpd_wsgi.conf

-rw-r--r-- 1 root wheel 883 27 May 2014 httpd_xcsweb_xcode.conf

drwxr-xr-x 2 root wheel 68 14 May 2014 other

-rw-r--r-- 1 root wheel 21424 24 Jul 15:04 servermgr_web_apache2_config.plist

-rw-r--r-- 1 root wheel 602 27 May 2014 servermgr_web_apache2_config.plist.default

drwxr-xr-x 11 root wheel 374 24 Jul 15:04 sites

drwxr-xr-x 5 root wheel 170 20 Nov 2014 sites_disabled

drwxr-xr-x 2 root wheel 68 25 Feb 2014 webapp_scripts

drwxr-xr-x 24 root wheel 816 20 Nov 2014 webapps

-rw-r--r-- 1 root wheel 181 24 Jun 2014 webdav_sharepoints.plist


Hi etresoft, im not planning on hosting sites for other people (don't think i'll use that feature myself even) as I do have sites with a proper host like you mention. I just want to use the wiki so that when Im at work (server is at home) I can put my notes/articles on the wiki. I work for a Cisco partner so I have a lot of syntax and explanations that I want to document.


On the plus side, in addition to the mac server going public with the wiki I am going to be using my Cisco 887 or 1841 to be the internal router and therefore having ACLS applied to stop unwanted traffic. Infant I could just allow my home network and my workplaces public static IP address even to really tighten down.


Many thanks,

Reply
User profile for user: Community User
Community User Author

Jul 25, 2015 9:31 AM in response to Linc Davis

Strange I just tested again to try and get fresh logs and not many logs outputted.


Heres what I have:


collaboration daemon

Jul 25 17:15:22 mercury.lmp.me.uk collabd[81554] <Info>: [main.m:377 75a31310 +116667ms] Interval since last HTTP activity: 116.766429 sec


wiki admin log:

Jul 25 00:00:10 mercury.lmp.me.uk wikiadmin[46322] <Info>: [CSExecutionTimer.m:14 75a31310 +0ms] TIMER: 1ms ---> numberOfRelatedDocuments

Jul 25 00:00:10 mercury.lmp.me.uk wikiadmin[46322] <Info>: [CSExecutionTimer.m:14 75a31310 +0ms] TIMER: 1ms ---> numberOfDistinctTags

Jul 25 00:00:10 mercury.lmp.me.uk wikiadmin[46322] <Info>: [main.m:516 75a31310 +1ms] Wikiadmin trying to stop PGCServer...

Jul 25 00:00:11 mercury.lmp.me.uk wikiadmin[46322] <Info>: [main.m:519 75a31310 +698ms] PGCServer succesfuly stopped...


Websites > error log - server SSL

[Fri Jul 24 14:58:27 2015] [warn] RSA server certificate CommonName (CN) `mercury.local' does NOT match server name!?

[Fri Jul 24 14:58:27 2015] [notice] Apache/2.2.26 (Unix) DAV/2 mod_ssl/2.2.26 OpenSSL/0.9.8zc configured -- resuming normal operations

[Fri Jul 24 14:59:52 2015] [notice] caught SIGTERM, shutting down

[Fri Jul 24 14:59:56 2015] [notice] Apache/2.2.26 (Unix) mod_ssl/2.2.26 OpenSSL/0.9.8zc DAV/2 configured -- resuming normal operations

[Fri Jul 24 15:04:06 2015] [notice] caught SIGTERM, shutting down

[Fri Jul 24 15:04:10 2015] [notice] Apache/2.2.26 (Unix) DAV/2 mod_ssl/2.2.26 OpenSSL/0.9.8zc configured -- resuming normal operations


websites > Access log

mercury.lmp.me.uk {ip here} - - [25/Jul/2015:17:13:26 +0100] "GET /__collabd/coreclientwiki/favicon1632.ico HTTP/1.1" 200 4257 “{server address}/“ "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5"


Nothing seems to reference the 404 error and I can still access it internally on https and accepting certificate.


Thanks for your help.

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Jul 25, 2015 11:16 AM in response to Community User

RSA server certificate CommonName (CN) `mercury.local' does NOT match server name!?

You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour. Then check the validity of the master's certificate. The common name must match the hostname and domain name. If necessary, delete all certificates and create new ones.

Reply
User profile for user: etresoft
etresoft
User level: Level 8
46,318 points

Jul 25, 2015 11:41 AM in response to Community User

~Luke wrote:


[Fri Jul 24 14:58:27 2015] [warn] RSA server certificate CommonName (CN) `mercury.local' does NOT match server name!?

Hello again ~Luke,

That sounds like the same kind of problem that caused me to give up on OS X Server. Server has a handful of cool tricks that only it can do. If you need those services, Server is the right choice. But strangely enough, any common internet services like DNS, Mail, or web are much easier to setup by hand on the client (standard) version of OS X. Here is my User Tip for doing just that: https://discussions.apple.com/docs/DOC-3083


My User Tip doesn't cover a secure server. I have setup my own secure server in the past using standard Apache techniques without many problems.

Reply
User profile for user: Community User
Community User Author

Jul 27, 2015 6:20 AM in response to etresoft

Hi etresoft, thanks for the article - I may go down thaty route if all else fails.



Hi Linc,


Its strange, I re-did the hostname bit because I remembered renaming previously rather than re-doing another a different type (private, domain etc),

It then appeared to work on my iPhone (on 3G/cellular),


However trying again just reported the original 403 error.

I have just re-done the cert (followed apple guide) but no change.


Common name does say the server domain.

Wiki ports 8085-8087 (443 and 80 already open)


no new errors in logs. COmmon name mismatch appears to have gone now.


Any more idea's?

Reply
User profile for user: Community User
Community User Author

Jul 30, 2015 4:40 AM in response to Linc Davis

Ignore that reply sorry - the HTTPS request was probably sent/processed before the WiFi disassociated.


Any idea what more I could check?


Thanks

Reply
User profile for user: Community User
Community User Author

Aug 3, 2015 6:02 AM in response to Linc Davis

Sorry... I confused with my last update.


When I browse to http://mysite.com/wiki it loads the wiki

but when I browse to https://mysite.com/wiki it gives error:

Not Found

The requested URL /wiki/ was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

date.dd I redid the cert following an apple guide.


Common name on cert does say the server domain.

Wiki ports 8085-8087 have been opened (443 and 80 already open)


No new errors in logs. Common name mismatch appears to have gone now.


Any other idea's?


Many thanks for your time.

Reply

How do you get wiki on HTTPS working?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up