also add that the front end log shows me this error [image: Captura de pantalla 2023-03-20 075206.png]
El lunes, 20 de marzo de 2023 a las 7:29:09 UTC-6, Jorge Alberto Bonilla Castaneda escribió: > good morning > > Well, that configuration works for me when we talk about a local network, > but when that configuration is already used in servers hosted in the cloud, > the front-end stops working > > verify that the required addresses are publicly accessible: > http://150.136.129.10:8983/solr/#/ > http://150.136.129.10:8080/server/#/server/api > > but the front end keeps giving the same error: > http://150.136.129.10/ > > [image: Sin título.png] > and my configuration is the following > > [image: Captura de pantalla 2023-03-20 072614.png] > What could it be ? > > El viernes, 17 de marzo de 2023 a las 16:37:26 UTC-6, Mohammad S. > AlMutairi escribió: > >> You don't need to use a self-signed certificate to continue your >> implementation ( You can use it but you don't have to ). Recent DSpace >> versions are forgiving. You can configure both DSpace ends using domain >> names using (http) or IP that's include private or public IP without SSL >> and DSpace still works. >> >> *** You need to stop the Webserver and have port 80 and 8443 publicly >> accessible for this to work. *** >> ** dspace.cfg or local.cfg >> dspace.server.url = http://server-public-ip:8443/server >> <http://server-public-ip:8080/server> >> dspace.ui.url = http://server-public-ip >> >> ** config.prod.yml >> ui: >> ssl: false >> host: server-private-ip >> port: 80 >> >> rest: >> ssl: false >> host: server-public-ip >> port: 8080 >> nameSpace: /server >> >> 1) yarn test:rest >> 2) yarn start:prod >> 3) Access DSpace at http://server-public-ip >> >> >> The above setup should keep you going till you get your public cert but >> If you still need to get the self-signed cert working you need to post the >> OS and the webserver you are using. Posting the reverse proxy will help. >> >> Mo. >> >> On Friday, March 17, 2023 at 5:58:41 PM UTC+3 Jorge Alberto Bonilla >> Castaneda wrote: >> >>> 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/cfe6c849-d9b4-4446-9f73-49d626a8b84cn%40googlegroups.com.
