Migration to https

144 views
Skip to first unread message

Milos Ivanovic

unread,
Feb 24, 2024, 1:58:22 AM2/24/24
to DSpace Technical Support
Dear All,

I have a strange problem with the backend after the migration of my DSpace 7.6.1 from http to https. Nginx and certificates are ok, the value in local.cfg is:

dspace.server.url=https://api.example.com

However, when I browse with the HAL browser for i.e. collection[0], I get something like:

   "dc.identifier.uri": [
            {
              "value": "https://example.com/handle/123456789/2",
....
            }
          ],
          ]
        },
        "archivedItemsCount": -1,
        "type": "collection",
        "_links": {
          "harvester": {
            "href": "http://api.example.com/server/api/core/collections/7e90beb5-6f1b-42df-a1e7-6367d1e508c2/harvester"
          },
          "itemtemplate": {
            "href": "http://api.example.com/server/api/core/collections/7e90beb5-6f1b-42df-a1e7-6367d1e508c2/itemtemplate"
          },
          "license": {
            "href": "http://api.example.com/server/api/core/collections/7e90beb5-6f1b-42df-a1e7-6367d1e508c2/license"
          },

As you see, the harvester, license, logo, etc. links are still HTTP-based. How to change this? Manually, or there is an automatic procedure? Due to this issue, the front end does not work, as well.

Thanks in advance!
Milos

Plate, Michael

unread,
Feb 24, 2024, 4:10:30 AM2/24/24
to DSpace Technical Support
Hi Milos,

you need to set both

dspace.server.url=https://<your-server>/server

and

dspace.ui.url = https://<your-server>

CU

Michael

________________________________________
Von: dspac...@googlegroups.com <dspac...@googlegroups.com> im Auftrag von Milos Ivanovic <imi...@gmail.com>
Gesendet: Samstag, 24. Februar 2024 07:58
An: DSpace Technical Support
Betreff: [Extern] [dspace-tech] Migration to https
[…]

Milos Ivanovic

unread,
Feb 24, 2024, 6:40:42 AM2/24/24
to DSpace Technical Support
Thank you for your quick reply. I resolved the problem. Your suggestion is, of course, required, but not enough. According to https://groups.google.com/g/dspace-tech/c/Y0bcDpSzIxc/m/UZKj3ypjBQAJ, I had also to add

proxy_set_header X-Forwarded-Proto https;

into my Nginx config.

Kind regards
MIlos
Reply all
Reply to author
Forward
0 new messages