In v11 beta7, new members can't sign in. I removed the requirement for captcha, but still no go. After filling in all the required info, clicking the button, it just sits there. From the Composr side, all I see is this warning when I log in as admin…


The admin account was created when the site was created, and it can log in just fine. I don't see any PHP errors in the logs. Maybe it's the server…I just don't know. Anyway, just sharing what happens with V11 so far. Lots of progress being made and I'll be interested to see beta8.

I'm literally just about to release beta8 so let's try to work this out before I do so a fix can be implemented.

403 means "forbidden". My server / composr.app blocked your site's attempt to connect to it for some reason.

Does the Admin Dashboard work / show that you are running the latest version of Composr? If so, it's an issue specific with the RSS feed. If not, the server is probably blocking your IP address.

PDStig said

I'm literally just about to release beta8 so let's try to work this out before I do so a fix can be implemented.

403 means "forbidden". My server / composr.app blocked your site's attempt to connect to it for some reason.

Does the Admin Dashboard work / show that you are running the latest version of Composr? If so, it's an issue specific with the RSS feed. If not, the server is probably blocking your IP address.

From “Post #8536”, 31st Jul 2025

admin logs in fine. In fact, everything else looks amazing. No new members can join, is all. That URL is missing a / right after https. Maybe that's it, or maybe it's a blacklist.

The single slash is a bug with rendering the URL in the error message.

You would have gotten a different error than 403 if the URL requested actually only contained a single slash; 403 means the request to the server was successful and the URL is valid, but the server didn't allow you to access it (e.g. "access denied").

So, to better clarify, you're saying that *joining* freezes, not *logging in*? If so, on what step? I'm assuming after you fill in username / password / etc.

Do me a favor, go in Admin Zone > Audit > Low-level logs. Activate the http log. Sign out. Try joining (let it time out if possible by letting it sit). Then *whisper* (so it's not public) your http.log file to me (click whisper on this post) so I can take a look and see if I can find anything.

Yeah it looks like this server is blocking your server's requests.

Do me another favor if you can. Whisper to this post your server's IP address so I can investigate further. Since I'm using Cloudflare, it's hard to tell which logs on my end match your server. But I am seeing 403s on my end. Thanks!

Yep...

Time for a hamburger. I'll try in about 45 minutes. Same errors.

Sent a PM.

Issue is that when an error occurs, sites send part of the error to composr.app to see if it's a common error. And Composr.app will respond with details if so. Problem is antispam heuristics often ban other sites when this happens because the errors contain links.

In beta8, this error service checking will be internally disabled. There is telemetry anyway, and we have a common errors page on composr.app under the support menu.

PDStig said

Sent a PM.

Issue is that when an error occurs, sites send part of the error to composr.app to see if it's a common error. And Composr.app will respond with details if so. Problem is antispam heuristics often ban other sites when this happens because the errors contain links.

In beta8, this error service checking will be internally disabled. There is telemetry anyway, and we have a common errors page on composr.app under the support menu.

From “Post #8551”, 31st Jul 2025

Looking forward to 11⁸