Hello, thanks for your answer, but even making that change, it still fails. Could it be that using self-generated insurance certificates is not correct? [image: Captura de pantalla 2023-03-17 142145.png] El viernes, 17 de marzo de 2023 a las 11:43:21 UTC-6, mmsz escribió:
> The Common Name (CN) in your certificate should mention the domain of the > server it is issued for. In case of i.e. 'localhost', the CN should be > 'localhost'. In your case, it should be the IP address 172.16.97.48 > piątek, 17 marca 2023 o 15:58:41 UTC+1 Jorge Alberto Bonilla Castaneda > napisał(a): > >> SSL issues >> >> Good morning, when I hosted my dspace 7.4 on the web, I realized that it >> is not possible to use the front-end if the back-end does not have a secure >> certificate. >> >> At the moment we can't get this certificate, but to continue with the >> implementation and configuration of it I wanted to use a self-generated >> certificate, so in a local copy of the machine in the cloud, I started >> trying, generating the certificate with keytool and doing the modifications >> in the urls of dspace.cfg and config.prod.yml >> >> Well now my back-end was using the 8443. >> [image: cer.png] >> >> however the front-end gave me the following error: >> [image: er.png] >> >> what could be doing wrong? Is it because it is a self generated >> certificate? >> >> -- *AVISO DE CONFIDENCIALIDAD:* Este mensaje y cualquier archivo adjunto al mismo, se dirige exclusivamente a su(s) destinatario(s), y no puede ser compartido o reenviado a un tercero sin autorización del remitente. Solo puede ser utilizado por las personas o entidades a las cuales está dirigido. Si usted no es el destinatario al que ha sido remitida esta información, queda prohibida, cualquier modificación, retención, difusión o copia total o parcial, y no puede emprender con ella ningún tipo de acción. Le rogamos que lo comunique inmediatamente por esta misma vía y proceda a su eliminación. Si es miembro de la Comunidad Educativa de la UDB y viola lo anterior será sujeto a sanción disciplinaria conforme al Art.134, literales “r”, “s”, y “t” del Reglamento General Administrativo-Académico. *CONFIDENTIALITY NOTICE:* The content of this email and any attachments are intended solely for the addressee(s). The information cannot be shared without the authorization of the sender. It can only be used by the intended recipients. If you are not the intended recipient, you are hereby notified that any modification, dissemination, full or partial copy of this email is forbidden. You must not take any kind of action in reliance on it. Please, notify the sender by replying to this email and delete the message without copying or disclosing it. If you are a member of the UDB community and were to violate the foregoing, you will be subject to disciplinary actions in accordance to Article 134, literal “r”, “s”, and “t” of the General Administrative-Academic Regulations. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/dd6f15ad-3e4e-4433-80df-01ee95d2c290n%40googlegroups.com.
