# CSRF problem in development with 'Discourse OpenID Connect' plug-in

**URL:** <https://meta.discourse.org/t/csrf-problem-in-development-with-discourse-openid-connect-plug-in/282786>\
**Category:** Development\
**Created:** [October 19, 2023, 12:05pm UTC](https://meta.discourse.org/t/csrf-problem-in-development-with-discourse-openid-connect-plug-in/282786 "2023-10-19T12:05:40Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![wayway\_way](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wayway_way/32/327018_2.png) [@wayway\_way](https://meta.discourse.org/u/wayway_way)\
**Post date:** [October 23, 2023, 3:25am UTC](https://meta.discourse.org/t/csrf-problem-in-development-with-discourse-openid-connect-plug-in/282786/7 "2023-10-23T03:25:25Z")

</div>

> [@simon](#):
>
> Probably not related to your issue, but maybe something that could cause issues for local development. I always use the `localhost:4200` domain. That seems to be what’s expected

Thanks, it works. 😊  
My workaround was to open discourse using 127.0.0.1:4200 instead of localhost:4200

---

_[View the full topic](https://meta.discourse.org/t/csrf-problem-in-development-with-discourse-openid-connect-plug-in/282786)._