Permalink url incorrect

[Poulter, Dale]

Good afternoon,

 

We are working to upgrade to 7.5.  The BE is working well using apache mod_proxy and is accessible from https://mybe.server.edu.  The FE is accessible through https://myfe.server.edu but the url for the items show http://localhost:4000/....  .  I have attempted several settings for mod_proxy including

 

    ProxyPass / http://localhost:4000/

    ProxyPassReverse / http://localhost:4000/

 

From the documentation.    Any suggestions?  Thanks.

 

 

-Dale

 

Dale Poulter Director, Library Technology and Digital Services Vanderbilt Libraries | Vanderbilt University 615-343-5388 | dale.p...@Vanderbilt.Edu | https://www.library.vanderbilt.edu Pronouns: he/him/his   My working day may not be your working day. Please do not feel obliged to reply to this email outside of your normal working hours.

 

 

[Michael Koch]

The information is stored in the meta attributes of the items (when these are created) - you have to change it there.

[Poulter, Dale]

Michael,

 

Thanks for the information.  It will be great when we are ready to correct the links.  The challenge is how to have these created correctly in the first place.  The  DSpace FE is seeing the url for the FE as localhost so it utilizes that for all links – even for handles.  Thanks again for your help.

 

 

 

-Dale

 

My working day may not be your working day. Please do not feel obliged to reply to this email outside of your normal working hours

 

--
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e852edb8-6d87-4c94-9416-319350128593n%40googlegroups.com.

[DSpace Technical Support]

Hi Dale,

I suspect you are missing either X-Forwarded-Proto or X-Forwarded-Host, which are noted as optional in the Installation guide.  However, for some setups, if these are not configured, then the UI will sometimes use "localhost" URLs.

You also should verify that the "dspace.ui.url" setting in the backend's local.cfg doesn't say "http://localhost:4000/".  It should have the public URL.

If neither of those help, then we may need more information about your setup.  It's also unclear where you see the localhost:400 URLs in the frontend...and that might provide clues as to where the misconfiguration may be.

Tim