At some point in the last 2 days internal URLs stopped oneboxing on my instance. I’m up to date with tests-passed as of 1:15 AM EST 6/9/17. There are the errors I’m seeing in the console when a post with an internal URL is loaded. There do not appear to be any related errors in /logs. [image]

Before I add a whitelist setting, one thing I realized is I should just whitelist the current host the site is on. If you are oneboxing the same discourse it should ignore those networking rules now: https://github.com/discourse/discourse/commit/a3729b51ebc9958904f15e5105754380de723997

Internal URL no longer oneboxing

Support

vinothkannans (Vinoth Kannan) June 9, 2017, 7:48am 6

I can reproduce the same problem even for external URL below. It returns same ‘404 not found’ error.

As it mentioned in another topic

Topic		Replies	Views
Onebox no longer works for my wordpress site Support	12	1663	June 12, 2017
Internal oneboxing problem revisited Support	6	921	July 10, 2017
Internal links stopped oneboxing in login-required instance Support	12	1580	July 4, 2016
What is the reason the source_topic_id that is added to internal oneboxes? Support	8	1437	February 13, 2018
Onebox redirects prevent linking to login-only content Feature onebox	13	1447	January 15, 2020

Internal URL no longer oneboxing

Related topics