Authentication problem after linux system upgrade

stuarthoughton8718 · 2021-06-24T07:58:00.000Z

Hi. I performed an apt-get upgrade on our spiceworks server today and it appears to have broken our helpdesk installation.

Following the update, anyone trying to log in gets redirected to an error page (URL: https://{hostname}/auth/identity/callback ) saying

"Oops! A Server Error Has Occurred.

Sorry! We’ve encountered a server application error.

You can contact us at help-desk-cloud-support@spiceworks.com and tell us about the problem you are having.

Once again, sorry about the problem, and thank you for your patience.

You can check out the status page or visit Spiceworks help pages for more information."

Several PAM-related package (libpam, etc.) were upgraded, which seems the most likely cause. Any ideas of how to fix this?

nickademus4070 · 2021-06-24T10:41:03.000Z

Have you tried reconfiguring the server script?

sudo tron-ctl stop
sudo tron-ctl reconfigure

Set the hostname to the computer name.

sudo tron-ctl start

I have no idea if this will fix your issue. I used to run Spiceworks on a Ubuntu Server 20.04.2 LTS but I ran into a irreconcilable bug with it and development for it is currently on hiatus: What’s going on with Spiceworks Tools & Apps in 2021?

“Some of you may have noticed we didn’t reference the Help Desk Server (HDS) above. Unfortunately, we do not see substantial interest or adoption of HDS, especially when compared to CHD. When we look at what we need to accomplish this year with CHD, we’ve come to the hard decision that our best path forward is to concentrate our efforts there. This means we’ll discontinue development on HDS during 2021 following the release of v1.3 and re-evaluate our position at the end of the year.”

Which stunk a little bit considering I just built it like 3 weeks ago lol. I’m migrating us over to the Cloud Based version this week.

I also know my server required libreadline7 instead of libreadline8 in order to function. Perhaps it upgraded that?
libread7 can be found here: Ubuntu – Error

stuarthoughton8718 · 2021-06-24T11:12:28.000Z

Nope, that didn’t work I’m afraid. Thanks anyway.

adamjohnsen · 2022-05-19T00:34:37.000Z

I’m having the same problem. I thought it was because of updating from HDS 1.2 to 1.3.4, but maybe not. I’m all upgraded, but cannot login and get the same error as OP. HDS is still working via email… I’m working with support on it and have just sent them the log files. Fingers crossed.

adamjohnsen · 2022-05-20T17:44:34.000Z

I’m running the OVA from HDS version 1.2. I upgraded to 1.3.4 and also upgraded the ubuntu itself. It’s on 20.04.x. When version 1.2 was release there was no real good way to change the portal url, so I followed the instructions to edit the production.rb file to comment out part of the file and add host = “mydomain.com” which solved the portal URL issue I had.

Well… After the upgrade to 1.3.4 it had wiped out any changes in the production.rb file that I made. So I made the changes (added host = “mydomain.com” and commented out the section after). I figured that’s how it was in 1.2. Turns out the same error in the OP I was getting after the update.
Much troubleshooting later (expanded drive to 20GB, expanded ram to 4GB), sent logs to support and tried tons of stuff I figured setting the production.rb back to defaults.
Then I ran sudo tron-ctl configure (when the service was stopped using sudo tron-ctl stop) and set the hostname there - not in the production.rb file voila! I was able to log back in the portal and no longer had the OP error.