Thank you very much Tim. The issue was indeed with the ssl cert. Apparently, all let's encrypt root certificates has expired on 30th September. Creating a new certificate solved the issue.
On Tuesday, 12 October 2021 at 20:43:15 UTC+3 caju...@gmail.com wrote: > I can't say for sure what's going on, but I do recall there are cases > where Java uses it's own Root CA Certificate store, separate from the OS. > And that (while we aren't using it) PHP sometimes benefits from an explicit > path... sometimes. What I mean to say is that not all CA stores are created > equally. And when those things are not all aligned properly, we get a SSL > trust error. I thought I saw a log file somewhere that indicated as such, > before I turned off all SSL. > > Since we know that it works with SSL turned off across the board, then > turning it on means that's where the error lies. Find all the logs you can, > especially [dspace]/logs/* and see what is happening there. Make sure the > log levels are set correctly in log4j2.xml, too. > > I will be pursuing this in the coming days and I will be using self-signed > certificates with a local Root CA certificate for our internal network. > Right now, I'm working on debugging something else. :) > > --Joel > > > > On Tuesday, October 12, 2021 at 12:45:38 PM UTC-4 Tim Donohue wrote: > >> This issue is puzzling to me, as it sounds like it should work. >> >> It makes me wonder if there's a possible SSL Certificate "trust" >> issue....where the frontend (running on Node.js) is not *trusting* the SSL >> Certificate that your backend is returning. We *have* seen this before, >> but in the past it was always with a self-signed SSL Cert. We have a >> couple of general notes on a workaround here: >> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-UsingaSelf-SignedSSLCertificatecausestheFrontendtonotbeabletoaccesstheBackend >> >> However, I admit, I'm not 100% sure if this is the issue. >> >> As a sidenote, per Mohammed's site, I've tried updating my local copy of >> Angular UI (running the latest code) by just updating one line of my >> "environment.common.ts" file to say "host: 'dspace.uobaghdad.edu.iq'". >> I've then run "yarn start", and my UI comes up on http://localhost:4000/ >> displaying the public content available at >> https://dspace.uobaghdad.edu.iq/server/. So, I cannot even reproduce >> this "no _links section" error if I run in production mode locally. >> >> I'm a bit confused what could be going on, but it seems like it might be >> an SSL cert trust issue or it might be a configuration error. Have you >> also double checked you are running a supported version of Node.js and >> Yarn? >> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-InstallingtheFrontend(UserInterface) >> >> >> Tim >> >> On Monday, October 11, 2021 at 5:06:58 AM UTC-5 jan.b...@gmail.com wrote: >> >>> Hi Mohammed, >>> you have exactly the same problem. >>> Jan >>> >>> On Monday, October 11, 2021 at 11:43:55 AM UTC+2 Mohammed Al-Shammaa >>> wrote: >>> >>>> Hi, >>>> I have installed DSpace 7 successfully, and it was working fine, >>>> however, suddenly it is giving the "No _links section found" error. I >>>> tried >>>> to "yarn start" and it was run without any errors: >>>> >>>> Building production environment >>>> Angular environment.ts file generated correctly at >>>> ./src/environments/environment.ts >>>> >>>> but the problem still exists. >>>> >>>> https://dspace.uobaghdad.edu.iq/ >>>> >>>> Any help to solve this issue is really appreciated. >>>> >>>> On Monday, 11 October 2021 at 12:19:05 UTC+3 jan.b...@gmail.com wrote: >>>> >>>>> To Tim: perhaps I can let you enter on our virtual machine if you agree >>>>> Jan >>>>> >>>>> On Monday, October 11, 2021 at 11:15:08 AM UTC+2 Jan Broulím wrote: >>>>> >>>>>> Dear Joel, >>>>>> I tried different certification authority, but it did not help. >>>>>> DSpace still works only in dev mode. >>>>>> But somehow it can be connected - when I was testing it on 2 machines >>>>>> without SSL, it was working properly. >>>>>> Thanks >>>>>> Jan >>>>>> >>>>>> On Friday, October 8, 2021 at 1:43:05 PM UTC+2 caju...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Jan and Tim, >>>>>>> >>>>>>> I'm going to offer some extra information that might help future >>>>>>> people. I was (am) testing this on a development server with >>>>>>> self-signed >>>>>>> TLS certificates and that was also causing this error to occur. Since >>>>>>> am >>>>>>> on a development server, I switched everything to SSL=false, and HTTP >>>>>>> instead of HTTPS and that mostly solved the problems I was having. I >>>>>>> will >>>>>>> pursue the problem later, but I may need to add my organization's >>>>>>> internal >>>>>>> Root CA Certificate to my development server and continue testing. >>>>>>> >>>>>>> Of course I had to update all of my settings to match (local.cfg, >>>>>>> environment.dev.ts, etc) >>>>>>> >>>>>>> I don't think a LetsEncrypt Cert would cause this problem, but you >>>>>>> never know. >>>>>>> >>>>>>> --Joel Richard >>>>>>> Smithsonian Libraries and Archives >>>>>>> >>>>>>> On Monday, October 4, 2021 at 1:08:06 PM UTC-4 jan.b...@gmail.com >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Tim, >>>>>>>> >>>>>>>> the files are identical (I also tried a copy of environment.dev.ts >>>>>>>> to environment.prod.ts), which did not help. >>>>>>>> >>>>>>>> It looks very strange for me, the guide >>>>>>>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22No_linkssectionfoundat...%22errorfromUserInterface >>>>>>>> >>>>>>>> probably will be useful. >>>>>>>> >>>>>>>> Installed on Debian. >>>>>>>> >>>>>>>> Jan >>>>>>>> >>>>>>>> >>>>>>>> On Monday, October 4, 2021 at 5:32:04 PM UTC+2 Tim Donohue wrote: >>>>>>>> >>>>>>>>> Hi Jan, >>>>>>>>> >>>>>>>>> We have a guide for that error here: >>>>>>>>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22No_linkssectionfoundat...%22errorfromUserInterface >>>>>>>>> >>>>>>>>> That said, your REST API at https://sulis53.zcu.cz/server/ "looks >>>>>>>>> correct" to me, and you can see that it has a "_links" section in the >>>>>>>>> response. >>>>>>>>> >>>>>>>>> Therefore, I highly suspect something is wrong with your >>>>>>>>> environment.prod.ts. Are you SURE it's identical to >>>>>>>>> environment.dev.ts? >>>>>>>>> Maybe there's a stray comma or odd space or something that is causing >>>>>>>>> issues when the configuration is read by `yarn start`? When `yarn >>>>>>>>> start` >>>>>>>>> runs, does it say it's using environment.prod.ts, or does it have a >>>>>>>>> message >>>>>>>>> like "No specific environment file found..." (if it's the latter, >>>>>>>>> that >>>>>>>>> means it's having issues reading your environment.prod.ts) >>>>>>>>> >>>>>>>>> It's not immediately obvious to me what the problem is...which is >>>>>>>>> why I immediately suspect it might be an invalid config file or >>>>>>>>> similar. >>>>>>>>> >>>>>>>>> If you are able to figure out the problem, please do let us know. >>>>>>>>> That way we can also update our guide about other issues that might >>>>>>>>> cause >>>>>>>>> this "No _links section found" error. >>>>>>>>> >>>>>>>>> Tim >>>>>>>>> >>>>>>>>> On Monday, October 4, 2021 at 10:23:09 AM UTC-5 jan.b...@gmail.com >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> we are installing DSpace7 and unfortunately have problems, which >>>>>>>>>> we are not able to explain or even resolve. >>>>>>>>>> >>>>>>>>>> Environment file and apache configuration is attached below. >>>>>>>>>> >>>>>>>>>> When running "yarn start:dev", it seems to be working, but when >>>>>>>>>> running "yarn start" (environment.prod.ts and environment.dev.ts are >>>>>>>>>> the >>>>>>>>>> same), we always get "no _links section found..." error. >>>>>>>>>> >>>>>>>>>> Could you please help us to resolve the problem? What might be >>>>>>>>>> the difference, which can cause this problem? >>>>>>>>>> >>>>>>>>>> You can even check - "No _links section found at >>>>>>>>>> https://sulis53.zcu.cz/server/api";, but this link is normally >>>>>>>>>> accessible. >>>>>>>>>> The testing instance runs here: https://sulis53.zcu.cz: >>>>>>>>>> >>>>>>>>>> Thank you >>>>>>>>>> >>>>>>>>>> With regards >>>>>>>>>> >>>>>>>>>> Jan >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------- >>>>>>>>>> environment.*.ts: >>>>>>>>>> >>>>>>>>>> export const environment = { >>>>>>>>>> ui: { >>>>>>>>>> ssl: false, >>>>>>>>>> host: 'localhost', >>>>>>>>>> port: 4000, >>>>>>>>>> nameSpace: '/' >>>>>>>>>> }, >>>>>>>>>> rest: { >>>>>>>>>> ssl: true, >>>>>>>>>> host: 'sulis53.zcu.cz', >>>>>>>>>> port: 443, >>>>>>>>>> nameSpace: '/server' >>>>>>>>>> } >>>>>>>>>> }; >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> apache: >>>>>>>>>> <VirtualHost _default_:443> >>>>>>>>>> SSLEngine on >>>>>>>>>> SSLCertificateFile /etc/letsencrypt/live/ >>>>>>>>>> sulis53.zcu.cz/cert.pem >>>>>>>>>> SSLCertificateKeyFile /etc/letsencrypt/live/ >>>>>>>>>> sulis53.zcu.cz/privkey.pem >>>>>>>>>> >>>>>>>>>> ProxyPass /server http://localhost:8080/server >>>>>>>>>> ProxyPassReverse /server http://localhost:8080/server >>>>>>>>>> >>>>>>>>>> RequestHeader set X-Forwarded-Proto https >>>>>>>>>> >>>>>>>>>> ProxyPass / http://localhost:4000/ >>>>>>>>>> ProxyPassReverse / http://localhost:4000/ >>>>>>>>>> >>>>>>>>>> </VirtualHost> >>>>>>>>>> >>>>>>>>> -- 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/fc8837a4-72a8-42fa-aeee-af724ea54ad1n%40googlegroups.com.
