"Something went wrong. Please try again"

[gp-Airee]

on IPS cloud installation. see my forums @ forums.juicylandgaming.com to see the error.
it sometimes works, it sometimes doesn't. let me know if there are any logs that you need.

[itsAliAvali]

should have a log printed for it in System Error or Error Logs... and what action is being taken to get this error to occur? logging in? registering? acp login?

[itsAliAvali]

I was able to register with steam just fine without error, logged out and back in without issue as well.

---

also whats the app you use to prompt steam only login?

[Hyrius]

I'm having the same issue.
Please note that this is using IPB 4.2.0.

EDIT: Fresh IPB 4.2.0 installation, only plugin installed is this one.

[LavaToaster]

At some point this week I'm going to be performing an upgrade to 4.2.0 on a site I help maintain, I'll look into at that time.

[Hyrius]

I just updated my IPB to 4.2.1, and it seems to be working again.
Can you confirm, @Fiiily?

[MStruntze]

@Hyrius still seems to be an issue now and then. Fresh install with 4.2.1 and this plugin errors quite a lot (something went wrong) when attempting to register.
No errors seem to be generated in logs.

[Hyrius]

@MStruntze Agreed. I get errors sometimes, too.

[Hyrius]

@Lavoaster Sorry to disturb, but... Any news on this one? :)

[gp-Airee]

@madman32395 Hey, how's it going? I'm sorry for getting back to you late.
The issue is resolved with recent IPS updates and I am using template modifications to lock you into using Steam authentication.

[robinlahtinen]

Same issue.

[toorisrael]

I've got this error every time

I can confirm this, no sign-in possible.
The plugin pulls the profile picture from steam but signing in is not possible. There are no error logs written. I count this as critical
IPB 4.2.5

EDIT: Funny behaviour: I was able to log in via steam, but I noticed a design flaw. I checked my settings and saw that the plugin was disabled (activated as login handler, disabled as plugin). After enabling it as plugin it had the same error as mentioned above.

EDIT2: After disabling and re-enabling the login handler it works again. I absolutely cannot reproduce the error, but I will watch the behaviour.

EDIT3: It works only random. Sometimes you have to try it several times and then from one second to another you're logged in. The tries before: see above error. Still no error logs