Thank you Tim thank u thank u..... It was just the capital letter issue and it worked and opened.... Thankssss muchhhh
On Fri, Dec 8, 2023, 5:35 PM DSpace Technical Support < dspace-tech@googlegroups.com> wrote: > Hi, > > Nothing stands out as completely wrong, but it can be difficult to notice > small typos or mistakes by just reviewing configs. So, it's always > possible I'm overlooking something and someone else on this list will > notice an issue. > > Have you tried accessing the REST API directly? Is it available at > https://HaigRepository.haigazian.edu.lb/server and working similar to our > demo site at https://demo.dspace.org/server/ > > Have you tried using the "yarn test:rest" commandline tool (which comes > with the User Interface) to see if it reports any bugs? This is > recommended in the "Common Installation Issues" that I linked you to > earlier. > > You also may want to try using URLs which have *no capital letters*. > That's a best practice for Search Engine Optimization. It also could cause > issues in proxying because URLs are case sensitive. So, if something is > trying to access https://haigrepository.haigazian.edu.lb/, it will NOT > find https://HaigRepository.haigazian.edu.lb/ These are *different URLs* > > My recommendation is to see if you can get the REST API working *first* & > looking like the demo site. This may mean commenting out EVERYTHING > related to the User Interface temporarily. Once the REST API is working, > then go back and add back in the configurations for the User Interface. > That may help you discover the core problem more easily then trying to do > both at the same time. > > Tim > On Friday, December 8, 2023 at 1:28:30 AM UTC-6 vghorg...@gmail.com wrote: > >> Dear Tim, >> That is the problem because when it is loading and after some time it >> gives the proxy error below the dev tools are not showing any error >> whatsoever. I checked the documentation also that you provided none of the >> errors are listed in it since the devtools are not showing any ... Apache >> 24 is showing the error below i went back a couple of versions with Apache2 >> i am getting the following error below. >> >> *Apache24* >> "Proxy Error >> The proxy server received an invalid response from an upstream server. >> The proxy server could not handle the request >> Reason: Error reading from remote server" >> >> *Apache2* >> Proxy Error >> The proxy server received an invalid response from an upstream server. >> The proxy server could not handle the request GET /reload/1701956886276. >> Reason: Error reading from remote server >> >> The only error that i am getting is in the apache logs is this below does >> it give you a hint of how i can solve this issue ? >> [Fri Dec 08 09:11:07.422110 2023] [proxy_http:error] [pid 9304:tid 1244] >> (OS 10060)*A connection attempt failed because the connected party did >> not properly respond after a period of time, or established connection >> failed because connected host has failed to respond. * : [client >> 192.168.40.165:24224]* AH01102: error reading status line from remote >> server localhost:4000, referer:* >> https://haigrepository.haigazian.edu.lb/home >> [Fri Dec 08 09:11:07.422110 2023] [proxy:error] [pid 9304:tid 1244] >> [client 192.168.40.165:24224] AH00898: Error reading from remote server >> returned by /favicon.ico, referer: >> https://haigrepository.haigazian.edu.lb/home >> >> I searched all over the web and didn't find any solution yet... Please I >> am putting my configuration if you can just take a look, posting the >> important sections >> *local.cfg* >> dspace.server.url = https://HaigRepository.haigazian.edu.lb/server >> dspace.ui.url = https://HaigRepository.haigazian.edu.lb >> proxies.trusted.ipranges = 192.168.4.4 >> rest.cors.allowed-origins = ${dspace.ui.url}, http://localhost:4000 , >> http://192.168.4.4:8080 , http://192.168.4.4:4000 , >> http://HaigRepository.haigazian.edu.lb:4000 , >> http://HaigRepository.haigazian.edu.lb:8080 , https://192.168.4.4 >> >> *Config.prod.yml* >> ui: >> ssl: false >> host: localhost >> port: 4000 >> nameSpace: / >> rateLimiter: >> windowMs: 60000 # 1 minute >> max: 500 # limit each IP to 500 requests per windowMs >> useProxies: true >> >> rest: >> ssl: true >> host: HaigRepository.haigazian.edu.lb >> port: 443 >> nameSpace: /server >> >> *dspace.angular.json* >> { >> "apps": [ >> { >> "name": "dspace-angular", >> "cwd": "c:\\dspace-angular-dspace-7.6", >> "script": "dist\\server\\main.js", >> "instances": "max", >> "exec_mode": "cluster", >> >> "env": { >> "NODE_ENV": "production", >> "DSPACE_REST_HOST": "HaigRepository.haigazian.edu.lb", >> "DSPACE_REST_SSL": "true", >> "DSPACE_REST_PORT": "443", >> "DSPACE_REST_NAMESPACE": "/server" >> } >> } >> ] >> } >> >> *For the proxy, the SSL file that I have included in the main httpd.conf >> is as follows* >> >> <VirtualHost *:80> >> ServerName HaigRepository.haigazian.edu.lb >> Redirect / https://HaigRepository.haigazian.edu.lb >> </VirtualHost> >> <VirtualHost _default_:443> >> >> DocumentRoot "${SRVROOT}/htdocs" >> >> ServerName HaigRepository.haigazian.edu.lb >> ServerAdmin ad...@example.com >> >> ProxyRequests on >> SSLEngine on >> SSLProxyEngine on >> >> SSLCertificateFile "${SRVROOT}/conf/drlive.crt" >> SSLCertificateKeyFile "${SRVROOT}/conf/drlive.key" >> SSLCertificateChainFile "${SRVROOT}/conf/drlive2.cer" >> SSLCompression off >> SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1 >> SSLHonorCipherOrder off >> SSLSessionTickets off >> ProxyPreserveHost on >> RequestHeader set X-Forwarded-Proto https >> >> <Proxy *> >> AddDefaultCharset Off >> Require all granted >> </Proxy> >> >> ProxyPass /server http://localhost:8080/server >> ProxyPassReverse /server http://localhost:8080/server >> >> #SetEnv proxy-initial-not-pooled >> ProxyPass / http://localhost:4000/ >> ProxyPassReverse / http://localhost:4000/ >> >> </VirtualHost> >> >> >> *Any ideas ? thanks much * >> >> On Thursday, December 7, 2023 at 7:40:05 PM UTC+2 DSpace Technical >> Support wrote: >> >>> Hi, >>> >>> As I noted previously, if the User Interface either spins or gives a >>> blank page, you should also look for underlying errors *in the user >>> interface*. These can only be found in your browser's DevTools window, and >>> they may not always be captured in log files on the backend. Again, see >>> the Troubleshooting guide for tips on finding those errors: >>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) >>> >>> Without more details about the errors you can find, it's very difficult >>> for anyone to help. We'd have to make wild guesses. My best guess based on >>> what you've said is that either you have a configuration problem (which >>> should result in errors that are findable via the "Troubleshoot an error" >>> guide) or you have a Proxy configuration problem (which may be more >>> difficult to track down as that's not an issue in DSpace...it's an issue in >>> how Apache is configured). >>> >>> Tim >>> >>> On Wednesday, December 6, 2023 at 2:47:56 AM UTC-6 vghorg...@gmail.com >>> wrote: >>> >>>> Thanks Tim, yes i checked these but these sites are giving any solution >>>> .... the problem is the following >>>> my site is loading i.e dspace.ui.url = >>>> https://HaigRepository.haigazian.edu.lb >>>> i click the links it opens but then i go to the login ,i put a wrong >>>> username and paswword it says invalid ,but when i put the correct one it >>>> gives a blank screen hoping to open the page after login and it spins and >>>> spins ... and then i get proxy error ..... >>>> any other ideas of where to check ? >>>> thanks >>>> >>>> On Tuesday, December 5, 2023 at 10:34:17 PM UTC+2 DSpace Technical >>>> Support wrote: >>>> >>>>> Hi, >>>>> >>>>> That sounds like a possible Proxy configuration error in Apache. When >>>>> you search for " AH01102: error reading status line from remote server" in >>>>> Google, there are a lot of people reporting similar issues with setting up >>>>> an Apache Proxy. See for example >>>>> https://stackoverflow.com/questions/62854501/apache-server-reverse-proxying-another-apache-server-getting-ah01102-error-re >>>>> and >>>>> https://serverfault.com/questions/965602/apache-2-4-proxy-httperror-proxyerror >>>>> >>>>> Tim >>>>> On Tuesday, December 5, 2023 at 4:12:28 AM UTC-6 vghorg...@gmail.com >>>>> wrote: >>>>> >>>>>> anybody encountered such error or similar upon logging in dspace ? it >>>>>> spins and spins and gives proxy error ,but inside the apache logs there >>>>>> is >>>>>> this eror. >>>>>> >>>>>> (((([Mon Dec 04 15:43:04.317553 2023] [proxy_http:error] [pid >>>>>> 9904:tid 1200] (OS 10060)A connection attempt failed because the >>>>>> connected >>>>>> party did not properly respond after a period of time, or established >>>>>> connection failed because connected host has failed to respond. : >>>>>> [client >>>>>> 192.168.4.4:55931] AH01102: error reading status line from remote >>>>>> server localhost:4000, referer: >>>>>> https://haigrepository.haigazian.edu.lb/home >>>>>> [Mon Dec 04 15:43:04.317553 2023] [proxy:error] [pid 9904:tid 1200] >>>>>> [client 192.168.4.4:55931] AH00898: Error reading from remote server >>>>>> returned by /reload/1701697324288, referer: >>>>>> https://haigrepository.haigazian.edu.lb/home)))) >>>>>> >>>>>> On Tuesday, December 5, 2023 at 8:05:32 AM UTC+2 Vahe Ghorghorian >>>>>> wrote: >>>>>> >>>>>>> Dear Tim, and dear dspace community >>>>>>> i have read all available documentation but I'm not having any luck >>>>>>> in fixing the error, this is the error that i am getting inside the >>>>>>> Apache >>>>>>> logs if i want to minimize the error . can you please at least narrow >>>>>>> down >>>>>>> of where could be the error,or if there is anything wrong with the >>>>>>> files/config that i have sent. >>>>>>> (((([Mon Dec 04 15:43:04.317553 2023] [proxy_http:error] [pid >>>>>>> 9904:tid 1200] (OS 10060)A connection attempt failed because the >>>>>>> connected >>>>>>> party did not properly respond after a period of time, or established >>>>>>> connection failed because connected host has failed to respond. : >>>>>>> [client >>>>>>> 192.168.4.4:55931] AH01102: error reading status line from remote >>>>>>> server localhost:4000, referer: >>>>>>> https://haigrepository.haigazian.edu.lb/home >>>>>>> [Mon Dec 04 15:43:04.317553 2023] [proxy:error] [pid 9904:tid 1200] >>>>>>> [client 192.168.4.4:55931] AH00898: Error reading from remote >>>>>>> server returned by /reload/1701697324288, referer: >>>>>>> https://haigrepository.haigazian.edu.lb/home)))) >>>>>>> >>>>>>> On Monday, December 4, 2023 at 11:00:37 PM UTC+2 DSpace Technical >>>>>>> Support wrote: >>>>>>> >>>>>>>> Hi Vahe, >>>>>>>> >>>>>>>> I wanted to add a note here that it's very difficult for others to >>>>>>>> help if we don't know the underlying error. If you ever find the User >>>>>>>> Interface "loads and loads" (or spins) that is a sign that's it's >>>>>>>> erroring >>>>>>>> out. But, you can find it's error from your web browser by following >>>>>>>> the >>>>>>>> Troubleshooting guide at >>>>>>>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) >>>>>>>> >>>>>>>> We also have a lot of common installation issues documented (and >>>>>>>> their possible solutions) at >>>>>>>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues >>>>>>>> >>>>>>>> Tim >>>>>>>> >>>>>>>> On Friday, December 1, 2023 at 6:40:28 PM UTC-6 katy...@gmail.com >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Vahe, >>>>>>>>> >>>>>>>>> It is tricky for sure. Recently I put up my sample working >>>>>>>>> http-based configuration in this email trail here: Setting up >>>>>>>>> DSpace on Windows Server 2022 (google.com) >>>>>>>>> <https://groups.google.com/g/dspace-tech/c/iLqVN87ovLI/m/Ev6wNMYFAgAJ?hl=en> >>>>>>>>> Hopefully that will help! You will want to make sure that the >>>>>>>>> values in your config.yml match what is in your local.cfg, even the >>>>>>>>> port. >>>>>>>>> Note that it is possible to comment out port in local.cfg and you may >>>>>>>>> have >>>>>>>>> to do that to get it to match up with config.yml. >>>>>>>>> >>>>>>>>> I also had issues running PM2 from a separate deploy folder, >>>>>>>>> getting CORS errors. I only had success with PM2 when my .json file >>>>>>>>> was in >>>>>>>>> the root of my install/build folder (/opt/dspace-7-angular, for me). >>>>>>>>> Also >>>>>>>>> note that the naming of environment variables seems to have changed >>>>>>>>> for >>>>>>>>> version 7.6.1 of Dspace. Check the documentation to be sure. >>>>>>>>> >>>>>>>>> I'd also say, before trying to get things working with PM2, try >>>>>>>>> ensuring that they work with yarn (yarn start, yarn test:rest). >>>>>>>>> >>>>>>>>> Also, I couldn't get self-signed certs to work at all, not even >>>>>>>>> with the NODE_EXTRA_CA_CERTS, so be sure that when you switch to >>>>>>>>> HTTPS that >>>>>>>>> you have a truly valid cert from a recognized CA. >>>>>>>>> >>>>>>>>> That is what I've deduced so far, and I'm willing to be wrong on >>>>>>>>> things... >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Katy >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thursday, November 30, 2023 at 6:15:02 AM UTC-8 Vahe >>>>>>>>> Ghorghorian wrote: >>>>>>>>> >>>>>>>>>> If anyone please at least can give a hint ???? much appreciated ! >>>>>>>>>> i reverted back and removed the HTTPS. and using HTTP with the >>>>>>>>>> domain name >>>>>>>>>> the application opens ,i go to Login page and put the correct >>>>>>>>>> credentails >>>>>>>>>> and the page loads and loads and loads without bringing anything >>>>>>>>>> ....what >>>>>>>>>> could be the error ? >>>>>>>>>> >>>>>>>>>> On Thursday, November 30, 2023 at 8:09:47 AM UTC+2 Vahe >>>>>>>>>> Ghorghorian wrote: >>>>>>>>>> >>>>>>>>>>> *in local.cfg i am using * >>>>>>>>>>> dspace.server.url = >>>>>>>>>>> https://HaigRepository.haigazian.edu.lb/server >>>>>>>>>>> dspace.ui.url = https://HaigRepository.haigazian.edu.lb >>>>>>>>>>> dspace.ui.url = https://192.168.4.4 >>>>>>>>>>> rest.cors.allowed-origins = ${dspace.ui.url} , >>>>>>>>>>> http://localhost:4000 >>>>>>>>>>> *in config.yml* >>>>>>>>>>> ui: >>>>>>>>>>> ssl: false >>>>>>>>>>> host: localhost >>>>>>>>>>> port: 4000 >>>>>>>>>>> nameSpace: / >>>>>>>>>>> useProxies: true >>>>>>>>>>> >>>>>>>>>>> # The REST API server settings >>>>>>>>>>> # NOTE: these settings define which (publicly available) REST >>>>>>>>>>> API to use. They are usually >>>>>>>>>>> # 'synced' with the 'dspace.server.url' setting in your >>>>>>>>>>> backend's local.cfg. >>>>>>>>>>> rest: >>>>>>>>>>> ssl: true >>>>>>>>>>> host: HaigRepository.haigazian.edu.lb >>>>>>>>>>> port: 443 >>>>>>>>>>> # NOTE: Space is capitalized because 'namespace' is a reserved >>>>>>>>>>> string in TypeScript >>>>>>>>>>> nameSpace: /server >>>>>>>>>>> >>>>>>>>>>> *in the json file * >>>>>>>>>>> "env": { >>>>>>>>>>> "NODE_ENV": "production", >>>>>>>>>>> "DSPACE_REST_HOST": " >>>>>>>>>>> HaigRepository.haigazian.edu.lb", >>>>>>>>>>> "DSPACE_REST_SSL": "true", >>>>>>>>>>> "DSPACE_REST_PORT": "443", >>>>>>>>>>> "DSPACE_REST_NAMESPACE": "/server" >>>>>>>>>>> } >>>>>>>>>>> >>>>>>>>>>> anything missing please advise. >>>>>>>>>>> On Wednesday, November 29, 2023 at 6:57:27 PM UTC+2 Vahe >>>>>>>>>>> Ghorghorian wrote: >>>>>>>>>>> >>>>>>>>>>>> I have just installed dspace 7 on a windows 10 machine. >>>>>>>>>>>> Moreover i have installed a certificate as well.when i put the >>>>>>>>>>>> domain name >>>>>>>>>>>> the page is opening normally and if i browse all the links it >>>>>>>>>>>> opens, now >>>>>>>>>>>> when i log in if i put incorrect password it says invalid, but if >>>>>>>>>>>> i put >>>>>>>>>>>> correct one, it should take me to the page where i add community, >>>>>>>>>>>> items >>>>>>>>>>>> etc... Admin site that is.but the page keeps on loading and >>>>>>>>>>>> loading as if >>>>>>>>>>>> something is blocking it and than gives the error attached. Im >>>>>>>>>>>> stuck here >>>>>>>>>>>> and i need help already the installation and the certificate took >>>>>>>>>>>> a lot of >>>>>>>>>>>> time and i reached to thia stage i need ot fixed please. >>>>>>>>>>>> The tomcat also in the logs its giving this error. >>>>>>>>>>>> [proxy_http:error] [pid 7644:tid 1216] (os 10060)a connection >>>>>>>>>>>> attempt failed because the connected party did not properly >>>>>>>>>>>> respond after a >>>>>>>>>>>> period of time, or established connection failed because connected >>>>>>>>>>>> host has >>>>>>>>>>>> failed to respond. : [client 192.168.4.4:52293] ah01102: error >>>>>>>>>>>> reading status line from remote server localhost:4000, referer: >>>>>>>>>>>> (domain >>>>>>>>>>>> name) please help >>>>>>>>>>>> >>>>>>>>>>> -- > 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/78da73bc-e278-48ff-8da0-d11ec624e18bn%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/78da73bc-e278-48ff-8da0-d11ec624e18bn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAAFebuzg4X2Ci_ZUvr2hdCpp7XfQNG1Ev3Dihw6m-pavzs_2rQ%40mail.gmail.com.
