Good morning Nico, The only change I could see that needs to be done is in your local.cfg. Just remove the port numbers. If you loaded SSL already, just change to https://
dspace.server.url = http://localhost/server dspace.ui.url = http://localhost <http://localhost:4000/> Restart the frontend and backend, run nmap localhost, and see if port 4000 is open My default apache SSL config #DSpace Backend ProxyPass /server http://xxxxxxx:8080/server ProxyPassReverse /server http://xxxxxxx:8080/server #Angular UI ProxyPass / http:xxxxxxx:4000/ ProxyPassReverse / http://xxxxxxx:4000/ #solr ProxyPass /solr http://127.0.0.1:8983/solr ProxyPassReverse /solr http://127.0.0.1:8983/solr Hope this helps, Regards, Daan On Fri, May 24, 2024 at 11:00 PM Nico Lambrechts <[email protected]> wrote: > i have installed Dspace 7.6 on a new server. > this will be a production server running ssl, so i have installed apache > to proxy. > > from a network computer, I access https://dspace.domain, the site open > with error 500. > I access https://dspace.domain/server, the /server/api site open with no > problem. > > from the server i access http://localhost:4000 and the site open with no > problem. > http://localhost:8080/server and the site open with no problem. > > my config below: > local.cfg: > dspace.server.url = http://localhost:8080/server > dspace.ui.url = http://localhost:4000 > > config.prod.yml: > ui: > ssl: false > host: localhost > port: 4000 > nameSpace: / > > rest: > ssl: false > host: localhost > port: 8080 > nameSpace: /server > > apache: > dspace.conf > <VirtualHost _default_:443> > # Add your domain here. We've added "my.dspace.edu" as an example > ServerName dspace.domain > #.. setup your host how you want, including log settings... > > # Most installs will need these options enabled to ensure DSpace knows > its hostname and scheme (http or https) > # Also required to ensure correct sitemap URLs appear in /robots.txt > for User Interface. > ProxyPreserveHost On > RequestHeader set X-Forwarded-Proto https > > SSLEngine on > SSLCertificateFile /etc/ssl/certs/Cert2024.pem > SSLCertificateKeyFile /etc/ssl/private/Cert2024.key > > SSLHonorCipherOrder off > SSLSessionTickets off > ProxyPreserveHost on > RequestHeader set X-Forwarded-Proto https > > <Proxy> > AddDefaultCharset Off > Require all granted > </proxy> > > ProxyPass /server http://localhost:8080/server > ProxyPassReverse /server http://localhost:8080/server > ProxyPass / http://localhost:4000/ > ProxyPassReverse / http://localhost:4000/ > > </VirtualHost> > > > Please assist where and config i need to change to get the proxying to > work? > > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/1e0cd92c-5236-4643-adf3-f00c1eda62acn%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/1e0cd92c-5236-4643-adf3-f00c1eda62acn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > [image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&;> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&;> 25/05/24, 10:28:39 -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAJmvTcDXNkszpE-nh%3Dawoatfr1K5HCm8JThih_r-a6oJeUz3xQ%40mail.gmail.com.
