I am trying to say it looks like the problem is randomly happening in some URLs. In both topics it returning the same error. So it might be same issue.
I seem to recall that private topics don’t work for oneboxing - is that the issue you are experiencing with internal links?
That said, I can confirm I am getting identical 404 errors in the console for both internal links (linking to private topics in a private category) and namati.org links.
It’s normal for onebox to return the 404 error you’re seeing in the console above if it can’t retrieve the onebox, so I don’t think the error for internal oneboxes is the same as the external one.
I need better steps to reproduce this internal issue. (The external one linked before is good for me to investigate)
I don’t really have any more details at the moment. I’ll see what the results of your investigation with the external link are, then see if I need to get you more detail.
Well, here’s what I’ve got: it stopped working sometime in the last few days - it definitely worked previously as there are internal link oneboxes all over the forums. Nothing should have changed network wise on our end, but I’m reaching out to IT to check. External oneboxes (at least to other Discourse sites) still works.
When you say internal link, are you referring to links by IP address or internal hostnames? Because a recent security features is meant to disable SSRF attacks by ensuring redirects are to external services.
It’s possible we don’t see it here because external links resolve to a different IP than internal ones. If your network infrastructure is resolving the outer hostname to an internal IP internally that could cause it to stop working.