Thank you very much , what I have noticed is that the handle does not work for me since I made the change , if it worked before , it now throws me this error :
[image: Captura de pantalla 2023-03-27 134059.png] what could be the error ? El lunes, 27 de marzo de 2023 a las 12:35:04 UTC-6, Mohammad S. AlMutairi escribió: > You can safely ignore that 404 error. GA is disabled by default in DSpace > but if you need to enable it and use it follow the instructions you see > here > https://wiki.lyrasis.org/display/DSDOC7x/DSpace+Google+Analytics+Statistics#DSpaceGoogleAnalyticsStatistics-GoogleAnalyticsSupport > > Mo. > > On Monday, March 27, 2023 at 9:09:56 PM UTC+3 Jorge Alberto Bonilla > Castaneda wrote: > >> wait, I found this forum where instructions were given to fix the bug I >> ran into and they worked for me >> https://groups.google.com/g/dspace-tech/c/ba5O8lIpH1M/m/-ZgLFBOsAgAJ >> >> Now I only get a few errors like these, which I hope are not a big deal >> >> [image: Captura de pantalla 2023-03-27 120831.png] >> >> >> >> El lunes, 27 de marzo de 2023 a las 11:24:57 UTC-6, Jorge Alberto Bonilla >> Castaneda escribió: >> >>> Hello, apply what is mentioned in that forum that I send, that is, >>> configure my >>> >>> front end : https://rd.udb.edu.sv >>> backend : https://rd.udb.edu.sv/server/ >>> >>> with its DNS and corresponding security certificate and with its apache >>> configuration, however the back end keeps throwing me an error that doesn't >>> even let me do searches. >>> >>> [image: Captura de pantalla 2023-03-27 112118.png] >>> what is my mistake now? >>> >>> >>> in my dspace.cfg I have configured the following : >>> dspace.server.url = https://rd.udb.edu.sv/server >>> dspace.ui.url = https://rd.udb.edu.sv >>> rest.cors.allowed-origins = ${dspace.ui.url} >>> >>> in my config.prod.yml the following : >>> ui: >>> ssl: false >>> host: localhost >>> port: 4000 >>> nameSpace: / >>> >>> rest: >>> ssl: true >>> host: rd.udb.edu.sv >>> port: 443 >>> nameSpace: /server >>> >>> >>> and in apache .conf : >>> ProxyPass "/server" "http://localhost:8080/server"; >>> ProxyPassReverse "/server" "http://localhost:8080/server"; >>> >>> ProxyPass "/" "http://localhost:4000/"; >>> ProxyPassReverse "/" "http://localhost:4000/"; >>> >>> >>> >>> El jueves, 23 de marzo de 2023 a las 13:23:13 UTC-6, Mohammad S. >>> AlMutairi escribió: >>> >>>> Hi Jorge, >>>> >>>> You need to change your setup in dspace.cfg to read what you see below >>>> and then install apache or nginx and set it up as a reverse proxy. See the >>>> attached file in the link below for hints. >>>> in dspace.cfg I have defined the urls: >>>> dspace.server.url = https://rd.udb.edu.sv/server >>>> dspace.ui.url = https://rd.udb.edu.sv >>>> >>>> >>>> https://groups.google.com/g/dspace-tech/c/jDu1PyOEiKg/m/PdfiCloVAgAJ >>>> >>>> BR, >>>> >>>> Mo. >>>> On Thursday, March 23, 2023 at 8:43:07 PM UTC+3 Jorge Alberto Bonilla >>>> Castaneda wrote: >>>> >>>>> hello everyone >>>>> >>>>> I had already configured my dspace on a server in the cloud and with >>>>> its corresponding DNS, however, when I received the security certificate >>>>> and proceeded to configure it, only the back end worked for me: >>>>> https://rd.udb.edu. sv/ >>>>> >>>>> however the front-end from that moment throws me an error: >>>>> https://rd.udb.edu.sv:4000/ >>>>> >>>>> in dspace.cfg I have defined the urls: >>>>> dspace.server.url = https://rd.udb.edu.sv/server >>>>> dspace.ui.url = https://rd.udb.edu.sv:4000 >>>>> >>>>> and in config.prod.yml >>>>> ui: >>>>> ssl:true >>>>> host: 0.0.0.0 >>>>> port: 4000 >>>>> nameSpace: / >>>>> >>>>> rest: >>>>> ssl:true >>>>> host: rd.udb.edu.sv >>>>> port: 443 >>>>> >>>>> I am doing something wrong ? >>>>> >>>> -- *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/00761bee-98b6-4ae3-9e05-9f44af9ea5edn%40googlegroups.com.
