I’m trying to cross reference another post while replying to a post, it only posts the link and doesn’t create a OneBox embedded post. Is there any setting to enable this feature? I just see it a circle briefly as I post the thread link on the same forum and then it just stays as a link.

Can you try the latest Discourse? I made it so that oneboxing the same forum should always work: https://github.com/discourse/discourse/commit/a3729b51ebc9958904f15e5105754380de723997 I don’t think a setting is required.

This is VERY odd because it’s creating one boxes for posts from other websites or even from this forum, but links cross references within the same forum isn’t working, I just a animated circle next to the link and then it disappears. Any suggestions?

If your local ips resolve to a private ip range oneboxer will no longer process them for security reasons. We should probably have a setting for this @eviltrout . I wonder if the oneboxer should return a “cannot onebox local IPs” onebox to make it more clear this is happening?

[이미지] codinghorror: I wonder if the oneboxer should return a “cannot onebox local IPs” onebox to make it more clear this is happening This would be great. Also led me to investigate the DNS resolution. The DNS resolution of the server name wasn’t correct. Apparently Google’s DNS’s aren’t as …

[이미지] codinghorror: local ips resolve to a private ip range oneboxer will no longer process Are you saying that if the local machine has a private IP (e.g. is behind an AWS elastic IP) oneboxer won’t work? The machine has to have a public IP?

@eviltrout can explain Monday why this is a security risk and is locked down out of the box.

Okay thanks, looking forward to the patch to enable this for private IP’s. Is there a YAML setting or something I can use meanwhile.

I can explain right now. I’ve got a webserver right now running with two interfaces. One of those has port 80 and port 443 open to the outside world, and everything else locked down. The other interface is on a 10.x.y.z internal network. DNS resolution happens through here, and routing defaults to…

[이미지] RBoy: Are you saying that if the local machine has a private IP (e.g. is behind an AWS elastic IP) oneboxer won’t work? The machine has to have a public IP? @eviltrout how can I enable OneBox to use private IP’s to retrieve content? Is this a setting that can be made available (with a s…

Wow - I was only looking for a workaround, you guys are awesome, thanks!

Cross referencing a post doesn't create onebox

Product Support

eviltrout (Robin Ward) 6월 12, 2017, 2:57오후 10

You have to be patient - jeff only suggested a setting 16 hours ago. I will get it done today.

Internal URL no longer oneboxing

글		댓글	조회수
OneBox not working for domain names on same host IP Product Support	5	788	12월 15, 2021
Onebox preview isn't shown for my own blog Product Support onebox	3	349	6월 29, 2024
Internal oneboxing problem revisited Product Support	5	1047	7월 10, 2017
Internal links stopped oneboxing in login-required instance Product Support	11	1768	6월 22, 2016
Self Link previews not showing for private sites? Bug	14	3698	11월 3, 2016

Cross referencing a post doesn't create onebox

Related topics