Error logging into spiceworks service

sistemasvh · 2024-08-07T19:47:03.477Z

Hi everyone!! I have the error that I can’t finish configuring the Spiceworks Server application on a Windows Server 2012. I have a Windows Server 2012 that had the Spiceworks service installed and working correctly and out of nowhere I got an error that I don’t have an internet connection and that I should connect to a proxy. I uninstalled and reinstalled the Spiceworks service and when it asks me for my email and login password it tells me that I should connect to a proxy. I inform you that we don’t have any type of proxy on the network. Could you help me? Attached screenshot

Captura desde 2024-08-07 16-30-07866×659 97.9 KB

Rod-IT · 2024-08-07T20:46:00.127Z

Sistemasvh:

I have the error that I can’t finish configuring the Spiceworks Server application on a Windows Server 2012.

Spiceworks desktop 7.5 has not been supported for a couple of years now, it can no longer connect to the backend as it’s been taken down, you shouldn’t be using this any more.

Also, 2012 is way out of support, why have you not moved on from that?

There is no way around your issue, but you could try disconnecting the machine from the internet and see if it will let you login with cached credentials.

Rod-IT · 2024-08-07T20:46:51.430Z

Update [Nov 9, 2023]: As a part of the continued degradation of supporting services for the Desktop app, on Dec 1, 2023, we will take services offline, impacting the below functionality on all Desktop apps.

Desktop apps will be unable to generate alert notification emails or any other emails currently being sent by Spiceworks mail services.
Desktop apps will be unable to authenticate using Spiceworks authentication services (you will be unable to add new Desktop app users, register new installations of the Desktop app, manage/reset user passwords with Spiceworks authentication services).
Desktop app will be unable to install shared plugins, shared reports, or shared language packs from the Spiceworks App Center.
There may be other unanticipated effects on Desktop apps, potentially including impacts to core functionality. As we communicated in Dec. 2021, we recommend migrating off of the Desktop application.

What’s going on with Spiceworks Tools & Apps in 2021? - Spiceworks Support - Spiceworks Community

merlinyoda · 2024-08-08T01:14:49.782Z

You should not have uninstalled Spiceworks Desktop as this likely wiped out the corresponding SQLite database that it uses (and the local cache of passwords along with it). You could have safely ignored that error and continued using a majority of the functionality of the software (that’s what I do). If the software was configured to do regular backups, then there’s a decent chance you can get back to a working installation again.

I still use the Spiceworks Desktop even though it is unsupported and some functionality (like the Knowledge Base) no longer works without cloud support so I can confirm that I am still about to log into the interface because of the local caching of the password. As noted by @Rod-IT above, we likely will not be able to add any users though … unless, that is, I can reverse engineer what hashing algorithm was used to store them and set users up by directly editing the corresponding SQLite database directly.

mad-spicehead · 2024-08-12T20:53:52.841Z

Do you have a ‘test’ environment of Spiceworks installed on another server or even a Windows 10/11 workstation?

I had a few backup installations and simply was able to take my backups and restore to the new environments.

I get the proxy error on startup/login but can cancel because my login was cached as some other posters have said.

Ultimately if you have an image of your server from a while back, perhaps you can replicate that image onto another box and import the Spiceworks backup files to it?