# Can't access NC locally with external domain

**URL:** <https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409>\
**Category:** ℹ️ Support\
**Created:** [July 3, 2020, 10:46am UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409 "2020-07-03T10:46:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arthur\_Dent](https://help.nextcloud.com/user_avatar/help.nextcloud.com/arthur_dent/32/26788_2.png) [@Arthur\_Dent](https://help.nextcloud.com/u/Arthur_Dent)\
**Post date:** [July 3, 2020, 10:46am UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409/1 "2020-07-03T10:46:38Z")

</div>

Nextcloud version _(eg, 18.0.2)_:  
Operating system and version Ubuntu 20.04  
Apache or nginx version  
PHP version: 7.3.18

The issue you are facing:

Just set up NC for the first time. Got relevant ports open and port forwarding is working fine.

I have a dynamic DNS setup through no-ip which points to my NC server. There is an SSL certificate attached to the no-ip domain.

If I’m external to the local network, I can access NC absolutely fine using the no-ip domain. If im internal to the network, I can’t use the no-ip domain but can use via local IP address, albeit without SSL because theres no certificate for the local IP.

I have a pi-hole set up which works well and the no-ip domain is not blocked. My router (EE Smarthub) is set to use the pi-hole as DNS so all DNS requests are routed through the pi-hole

How do I use the external no-ip domain name internally?

Is this the first time you’ve seen this error? _(Y/N)_: Y

---

<div class="post-metadata">

**Author:** ![mad73](https://help.nextcloud.com/letter_avatar/mad73/32/6_22734026db12803ebb3e059622ac3534.png) [@mad73](https://help.nextcloud.com/u/mad73)\
**Post date:** [August 11, 2020, 11:05pm UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409/2 "2020-08-11T23:05:12Z")

</div>

I’m having this exact same problem (minus the pi-hole set up), and I can’t find information about this issue anywhere. Bump.

---

<div class="post-metadata">

**Author:** ![Arthur\_Dent](https://help.nextcloud.com/user_avatar/help.nextcloud.com/arthur_dent/32/26788_2.png) [@Arthur\_Dent](https://help.nextcloud.com/u/Arthur_Dent)\
**Post date:** [August 12, 2020, 7:01am UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409/3 "2020-08-12T07:01:53Z")

</div>

Hi mad73.

I actually figured it out myself.

You need to add a DNS entry for the host and related IP into your router or whatever system handles DNS. That way, whenever there’s a request by the hostname it will always get looped back to your internal IP

---

<div class="post-metadata">

**Author:** ![mad73](https://help.nextcloud.com/letter_avatar/mad73/32/6_22734026db12803ebb3e059622ac3534.png) [@mad73](https://help.nextcloud.com/u/mad73)\
**Post date:** [August 18, 2020, 12:14am UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409/4 "2020-08-18T00:14:23Z")

</div>

Thanks - that worked for me too.

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 12, 2024, 7:35am UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409/5 "2024-12-12T07:35:38Z")

</div>



---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 12, 2024, 7:35am UTC](https://help.nextcloud.com/t/cant-access-nc-locally-with-external-domain/86409/6 "2024-12-12T07:35:39Z")

</div>


