# 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:** [Juin 17, 2016, 12:54 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:** 3

<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:** [Juin 17, 2016, 6:52 UTC](https://meta.discourse.org/t/internal-links-stopped-oneboxing-in-login-required-instance/45949/3 "2016-06-17T18:52:43Z")

</div>

I just testet `curl`ing from both `google.de` and my domain itself from within the container, and the domain was resolved correctly. But Oneboxes are still not working (even for new links that are not in the cache)…

Any more ideas? Could I help you diagnose that in any way?

---

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