# Limitations on allowed origin

**URL:** <https://community.auth0.com/t/limitations-on-allowed-origin/9026>\
**Category:** Get Help\
**Tags:** ui\
**Created:** [December 20, 2017, 2:01am UTC](https://community.auth0.com/t/limitations-on-allowed-origin/9026 "2017-12-20T02:01:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhunter](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mhunter/32/7524_2.png) [@mhunter](https://community.auth0.com/u/mhunter)\
**Post date:** [December 20, 2017, 2:01am UTC](https://community.auth0.com/t/limitations-on-allowed-origin/9026/1 "2017-12-20T02:01:47Z")

</div>

This might be related to [Allowed web origins no longer accepts localhost origin - Auth0 Community](http://community.auth0.com/questions/12878/allowed-web-origins-no-longer-accepts-localhost-or) but I am posting it separately as it is different in the host part of the origin isn’t explicitly localhost.

We use hosts of the form [http://sitename.127.0.0.1.xip.io:9000/](http://sitename.127.0.0.1.xip.io:9000/) in our test environment. The UI accepts these as callback URLs but not origins. I get a message that said "The following URLs are invalid for the Web Origins property: [http://sitename.127.0.0.1.xip.io:9000/](http://sitename.127.0.0.1.xip.io:9000/)

[Note that I tried to post this once already and got myself to a an auth0 page where I got the auth0 oops page. So if this posting gets duplicated I am sorry.]

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [December 20, 2017, 6:05pm UTC](https://community.auth0.com/t/limitations-on-allowed-origin/9026/2 "2017-12-20T18:05:05Z")

</div>

Thanks for reporting this; it is indeed slightly different. I’ll review this and provide you with an update as soon as I have more information.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [December 20, 2017, 8:31pm UTC](https://community.auth0.com/t/limitations-on-allowed-origin/9026/3 "2017-12-20T20:31:13Z")

</div>

The situation was reproduced (yes, this one was easy to reproduce) and is now being tracked to be addressed. In addition to that possibility where the IP address is actually camouflaged as sub-domains it was also detected that simple IP addresses as the host were also not being allowed so the scope of the issue is to also address the standalone IP address situation.

As final note, have in mind that technically even after this is addressed the value `http://sitename.127.0.0.1.xip.io:9000/` contains a path component (`/` at the end) so it is not a web origin. The fix would however allow `http://sitename.127.0.0.1.xip.io:9000`.

As mentioned in the answer to the question you linked, it should be possible to bypass these validation hints that were not working as expected if you update the client settings through the management API, however, you then won’t be able to update that client through the dashboard.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:57am UTC](https://community.auth0.com/t/limitations-on-allowed-origin/9026/4 "2018-03-02T05:57:52Z")

</div>


