Users are reporting issues adding specific Discourse forums—particularly forum.image.sc and www.snuffhouse.com—to the Android DiscourseHub app, receiving “not found” errors. While some users confirm the issue persists across devices, others note success on iOS. Investigation reveals two root causes: for snuffhouse.com, a server-side 403 error blocks the app’s HEAD request to /user-api-key/new, likely due to CloudFront restrictions. For forum.image.sc, the issue was a misconfigured site setting (allowed crawler user agents) that blocked non-listed user agents—including the Android app’s. Adding the Android user agent to the allowed list resolved the issue for forum.image.sc. Other users, like Davim, report similar problems with their own sites, suggesting the issue may be widespread. Canapin tested and confirmed partial success across platforms, while pmusaraj provided technical diagnostics and confirmed the fix for forum.image.sc. Users are advised to check their site’s crawler settings or server configurations if encountering similar errors.
On my Samsung Galaxy A10 it couldn’t find it, but no issue adding it on iOS before that so it’s unlikely to be some weird DNS issue (I run my own DNS servers on my home network so guaranteed it was cached when Android tried to look it up)
Every time I or any user tries to add my website to the Discourse Hub mobile app, we get the error saying was not found. I have no Idea on how to fix that. I’ve seen many posts related to the same issue here, tried to implement their fixes but unfortunately none of them worked for me yet. Looking forward to get a more specific help for my case.
Thanks for the report, coincidentally the site was down at the time you tried. It was the SSL certificate that was renewing. That’s fixed and the site is up an running again, unfortunately, the issue on not finding the site on discourse hub isn’t fixed.
This looks to be a configuration error. The app does a HEAD request to https://www.snuffhouse.com/user-api-key/new first, and when I simulate the same, I get back an error:
We don’t host snuffhouse.com, so I’m not sure what in their stack is blocking these HEAD requests.
This one we do host and it was blocked from the hub because of a configuration issue. The site had some entries in the allowed crawler user agents site setting. That setting is quite heavy-handed, it comes with a big warning: User agents of web crawlers that should be allowed to access the site. WARNING! SETTING THIS WILL DISALLOW ALL CRAWLERS NOT LISTED HERE!
I added the Android user agent there, and that fixes the issue on my test Android device.