On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian wrote: > Thank you for the suggestion. I changed the dc.identifier.uri from > https://hdl.handle.net/your-handle-prefix/1916 by > https://my-server-domain-name/handle/my-handle-prefix/1916. Now, if I try > to open > https://my-server-domain-name/handle/my-handle-prefix/1916 in the > browser, I get 404 page not found. If I search for the item's title in all > of DSpace, and then try to download the pdf from there, I still can see the > pdf in the browser, but downloading it still doesn't work. > For this debugging session try to comment out *handle.canonical.prefix = https://hdl.handle.net/* in dspace.cfg and restart tomcat and see if that's help.
> In terms of Handle server, I wonder whether copy/pasting > [dspace]/handle-server directory's content from someone who has 7.4 on > Ubuntu 20.04 would fix my issue? > That's actually how I moved the handle server from the old server to the newer one not long ago and it worked. It will save you sending a newer generated sitebndl.zip to the HNR folks. 1) Copy the old [dspace]/handle-server folder from the old Windows server to the newer ubuntu server. 2) chown -R tomcat-user:tomcat-user [dspace]/handle-server 3) Check and change the private IP to the new private IP if it was changed in [dspace]/handle-server/config.dct 3) Check and change the public IP and the Private IP to match the new ones in [dspace]/handle-server/local_addresses 4) run [dspace]/bin/make-handle-config 5) start the handle server 6) check the handle server logs or run this command to see if it's running using ( ss -nlp | grep ":8000\|:2641" ) Hope it help On Friday, November 25, 2022 at 4:53:06 p.m. UTC-4 [email protected] wrote: > >> You should completely ignore that suggestion and here is why ( >> https://github.com/kiprotect/klaro ). I think the issue you have is >> caused by how the migration from the Windows server to the Linux was done >> and is related to the handle server specifically because it's down. As a >> suggestion try to change one of the the items >> (e56a5422-b32b-4000-95dd-86467ef21c35) dc.identifier.uri from >> https://hdl.handle.net/your-handle-prefix/1916 to >> https://your-server-domain-name/handle/your-handle-prefix/1916 and try >> to access it and download it and see if that helps isolate the handle >> server is the cause. >> >> Hope It help. >> >> On Friday, November 25, 2022 at 10:20:58 PM UTC+3 Night Librarian wrote: >> >>> I had a suggestion to disable klaro to solve a downloading problem on my >>> DSpace 7.4, but I am not sure how to do that. Can someone give me a hint? >> >> -- 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/e3e1c136-c70b-4176-a50b-65430b8ade99n%40googlegroups.com.
