DSpace 7.2 unable to login on frontend

[Lewatle Johannes Phaladi]

Dear DSpace Colleagues,

I have installed DSpace 7.2 and created initial admin user from 7.2 backend and when I try to logon to frontend it loads endlessly, please see attached screenshots.

Regards,

Lewatle  

[darryl....@usask.ca]

In that last screenshot it looks like you're mixing HTTP and HTTPS URLs.  I'd double check the config.*.yml files for frontend and the local.cfg on the backend, to ensure everything is matching up.

- Darryl

[Lewatle Johannes Phaladi]

Thanks a lot Darryl, I am rechecking the config files as you have indicated.

Regards,

Lewatle 

[Lewatle Johannes Phaladi]

Good Day,

please receive attached screenshots indicating config changes on both local.cfg and dspace.cfg files also the web interface results when trying to register user. 

in tomcat I have published backend using symbolic link, see results on attached file, hope that can give indication of where error comes from

Regards,

Lewatle 

[Tim Donohue]

Hi Lewatle,

Screenshots don't really help much to debug errors in DSpace 7.  It's much more useful to find the underlying error message text reported by either the UI or in the backend logs​.  See our Troubleshooting guide for information on finding the underlying error message: 

https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

In the screenshots you shared, the only one that gives a "clue" is the one that shows the red "POST" command returning a 405 response. 

However, the reason​ why it returns that error is unclear because you haven't looked at the backend logs to see if any errors were reported there.  A 405 error means that your REST API said that a POST request is "invalid"...but the reason may only be found in the backend logs.

As a sidenote, your "dspace.ui.url" should NOT include "/home".  Remove that subpath, as that also may cause issues (and it might even cause that 405 error, not sure).  "dspace.ui.url" should be the base URL of your site...and "/home" is not the base URL, instead that would be the URL of your site's homepage.

Good luck & let us know on this list what you find.

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Lewatle Johannes Phaladi <joem...@gmail.com>
Sent: Tuesday, April 12, 2022 8:51 AM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] Re: DSpace 7.2 unable to login on frontend

 

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/112ef21b-677b-4f9a-8e9c-51134411ea00n%40googlegroups.com.

[Lewatle Johannes Phaladi]

Hello Tim,

Much appreciated for help, I have removed /home on front end link from both local.cfg and dspace.cfg config files and restarted tomcat, after that I tried to login again from web interface and the page moved and tried to login but it remained with blank page loading without completion, I have attached dspace backend log file for additional details.

server url is placed  as follows in config files :

dspace.server.url = https://wiredspace-dev.wits.ac.za/server

Regards,

Lewatle 

[Tim Donohue]

Hi Lewatle,

There doesn't seem to be anything in the backend logs related to that 405 error. So, either the 405 is no longer occurring, or perhaps it was being caused by Tomcat directly? (Check your Tomcat logs as well for ERROR lines there).

You should also check to be certain that, after you made the configuration change, the error still a 405. Anytime you change the configuration it's possible that the exact error may change.  So, it's always possible that the config change fixed the 405 but that you are hitting a different error.

Again, see the troubleshooting guide for hints on locating errors in the UI or in logs: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Good luck,

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Lewatle Johannes Phaladi <joem...@gmail.com>

Sent: Thursday, April 14, 2022 5:07 PM

To: DSpace Technical Support <dspac...@googlegroups.com>

Subject: Re: [dspace-tech] Re: DSpace 7.2 unable to login on frontend

 

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/5f012412-6e3b-4f2b-9938-fb7934ad02can%40googlegroups.com.

[Lewatle Johannes Phaladi]

Hello Tim,

Amazing thing that is happening now, when I click on forgotten password and enter email address for admin user I receive  email to reset password, after resetting it then it allows me to logon to web interface but when I logout and login it refuses to load pages, if I do forgotten password steps again I am able to login, the initial admin user when logged in has no option to create collection, only item and since it is fresh installation item cannot be created while there is no collection or even initial community,  see attached screenshot logged in and no option to create community or collection.

Regards,

Lewatle 

[Tim Donohue]

Hi Lewatle,

Unfortunately screenshots don't help us determine the error.  It's impossible for anyone to tell what is going on based on a UI screenshot as the underlying error won't ever appear there.  So, screenshots are only useful to show that something is happening, but they won't ever show the reason why.

The only way to determine the cause behind an odd behavior is to again look for errors in the UI or backend logs.  Whenever you encounter odd behavior, that should be your first action, as it may lead you to the exact problem.

See our Troubleshooting guide for details: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Lewatle Johannes Phaladi <joem...@gmail.com>

Sent: Tuesday, April 19, 2022 8:21 AM

To: DSpace Technical Support <dspac...@googlegroups.com>

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/f0ab6e2f-9f45-4754-a580-abb32a12b03en%40googlegroups.com.

[Lewatle Johannes Phaladi]

Hello Tim,

I have attached copy of dspace.log file from backend.

Regards,

Lewatle 

[Tim Donohue]

Hi Lewatle,

Please always start by looking for UI-level errors in your browser's DevTools.  Most​ UI-level errors in DSpace 7 will not appear on the backend unless they are caused by a 500 response or similar backend error.

The logs you shared don't appear to show one of those errors.  You can search the logs yourself for any lines that include the text "ERROR" to locate issues. 

Again, please read & refer to our Troubleshooting guide for DSpace 7. It's important to get familiar with the troubleshooting process -- if you can quickly locate the error yourself, sometimes it's also very quick to find the solution by searching our mailing lists or "common installation issues".

https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Lewatle Johannes Phaladi <joem...@gmail.com>

Sent: Tuesday, April 19, 2022 2:22 PM

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/17aeab94-679d-4117-929e-d80024e2d384n%40googlegroups.com.

[Lewatle Johannes Phaladi]

Hello Tim,

Thanks a lot for assistance, testing rest  API gives attached results, I am also following on troubleshooting steps.

I have opted fresh install to reduce errors coming with Installation as running out of box software. 

Regards,

Lewatle