Self Link previews not showing for private sites?

[Joey_Tuan]

My link preview is just showing the URL and no link preview. Note: my website is a private instance. Any suggestions to get this working?

[codinghorror (Jeff Atwood)]

Private urls behind login cannot onebox.

[Joey_Tuan]

Is it possible to turn it off completely then, so I can show the full link?

[codinghorror (Jeff Atwood)]

Does it actually render like that if you post it though?

[Joey_Tuan]

Yup it renders exactly like that.

[codinghorror (Jeff Atwood)]

Can you repro this @techapj? We should not render a busted onebox when a password protected site oneboxes itself.

[techAPJ (Arpit Jalan)]

@codinghorror

Can you repro this @techapj?

Yes I can repro this, but only on private (login required) hosted instances.

The correct oneboxing behaviour in case of private instances is that the post gets oneboxed using local onebox class, but in case of private hosted instances this is not happening (it’s using WhitelistedGenericOnebox class instead).

I am looking into this issue and will post here with more updates.

[michael2 (Michael Marner)]

This issue is also affecting me. We are running the latest Discourse, using the standard Docker container on a Digital Ocean Ubuntu droplet.

[Falco]

I have a login required and I’m seeing this too.

If your queue is too long could you give me any directions to craft a PR?

[techAPJ (Arpit Jalan)]

Thanks Rafael!

The underlying issue is that in case of some Discourse instances (private hosted in my experience) the DiscourseLocalOnebox engine is not being used (which is responsible for oneboxing internal topics/posts)

https://github.com/discourse/discourse/blob/master/lib/onebox/engine/discourse_local_onebox.rb#L6

I can’t figure out why in some cases the above engine is not being used, will appreciate your help with this.

[Falco]

Hey @techAPJ, good and bad news!

First, the good news: It’s working on my instance.

Second: Looks like the rails method recognize_path doesn’t play along with rails config.relative_url_root. So my bug wasn’t related with being private at all. Maybe this is @Joey_Tuan case?

So, it’s a subfolder after all (I stump on subfolder bugs even when I’m looking somewhere else).

If we want to fix it at Discourse level we need:

diff --git a/lib/onebox/engine/discourse_local_onebox.rb b/lib/onebox/engine/discourse_local_onebox.rb
index 5fd4897..5e3b797 100644
--- a/lib/onebox/engine/discourse_local_onebox.rb
+++ b/lib/onebox/engine/discourse_local_onebox.rb
@@ -14,7 +14,7 @@ module Onebox
         if other.kind_of?(URI)
           uri = other
           begin
-            route = Rails.application.routes.recognize_path(uri.path)
+            route = Rails.application.routes.recognize_path(uri.path.sub(Discourse.base_uri, ""))
             case route[:controller]
             when 'uploads'
               super
@@ -34,7 +34,7 @@ module Onebox
 
       def to_html
         uri = URI::parse(@url)
-        route = Rails.application.routes.recognize_path(uri.path)
+        route = Rails.application.routes.recognize_path(uri.path.sub(Discourse.base_uri, ""))
         url = @url.sub(/[&?]source_topic_id=(\d+)/, "")
         source_topic_id = $1.to_i

And we have local oneboxing at subfolder install working.

[techAPJ (Arpit Jalan)]

Thanks Rafael! Awesome work

Can you send a PR with your fix? I’ll deploy and verify on private hosted Discourse instances.

[Falco]

https://github.com/discourse/discourse/pull/3991

PS.: Should this be fixed upstream on rails?

[techAPJ (Arpit Jalan)]

Just checked, this issue can still be reproduced on private (login required) hosted instances.

[zogstrip]

Should be fixed now

https://github.com/discourse/discourse/commit/a655e4b09259fa5a908416b0add303d7c710ac1f