[Archivesspace_Users_Group] SSL Redirect

[Trevor Thornton]

If you're following the example  you shouldn't add the port numbers to the
URL - staff.myarchive.org and research.myarchive.org (or whatever
subdomains you're using) should serve the frontend (staff UI) and public UI
respectively. SSL connections all happen over port 443, which is why you
have to use the subdomain redirects instead of using the standard port
numbers.

I think the point of Step 1 is to restrict non-SSL connections to the
default ports, which would otherwise be open by default.

I struggled with this myself but I had a sysadmin to help me get everything
configured correctly. Maybe somebody who is more well-versed in Apache
configuration will chime in with more info.



On Thu, Jan 11, 2018 at 10:35 AM, Fortney, Kyle <kyle.fortney at okstate.edu>
wrote:

> I am working on installing our SSL for our ArchivesSpace server.
> Unfortunately I cannot get the 8080 and 8081 redirects to work. I have
> followed the information in Step 2 at https://github.com/
> archivesspace/archivesspace/blob/master/README_HTTPS.md. Not sure how
> Step 1 is related. Our SSL is installed correctly as I can resolve the
> domain URL but using the domain name with the ports on the end fails. We
> are using Ubuntu 14.04 and Apache 2.4.7. Our AS instance is 1.5.1. Any
> insight would be appreciated.
>
>
>
> Kyle Fortney
>
> Computer Specialist
>
> 405-744-7924 <(405)%20744-7924>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180111/76e9d7ff/attachment.html>