# Internal links stopped oneboxing in login-required instance

**URL:** <https://meta.discourse.org/t/internal-links-stopped-oneboxing-in-login-required-instance/45949>\
**Category:** Product Support\
**Created:** [June 17, 2016, 12:54pm UTC](https://meta.discourse.org/t/internal-links-stopped-oneboxing-in-login-required-instance/45949 "2016-06-17T12:54:28Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [June 17, 2016, 10:02pm UTC](https://meta.discourse.org/t/internal-links-stopped-oneboxing-in-login-required-instance/45949/7 "2016-06-17T22:02:25Z")

</div>

Okay, I thought a bit more about the possible differences…

- Both sites ran the same version of Discourse.
- Both sites temporarily ran the exact same set of plugins for testing.
- The site settings in the `Onebox` category are identical.
- The site settings in the `Basic Setup` category are identical.
- The remaining site settings are not identical, but no difference seems related to oneboxing.
- The language settings in `app.yml` are identical.
- Both sites run under a nginx proxy handling SSL.
- Both sites are non-subfolder-installs.
- Of course, both sites are supported Docker installs.
- Both sites are running on Ubuntu 14.

Some differences:

- The site with the broken Oneboxes failed the automatic upgrade to Postgres 9.5.
- The site with the broken Oneboxes is running on a fourth-level domain; the other one is running on a third-level domain.

I’m not sure whether local oneboxes have ever been working in the broken instance.

---

_[View the full topic](https://meta.discourse.org/t/internal-links-stopped-oneboxing-in-login-required-instance/45949)._