# \[Paid\] User login issues -- improper https forwarding headers? **URL:** \ **Category:** Marketplace\ **Created:** [April 6, 2018, 6:04pm UTC](https://meta.discourse.org/t/paid-user-login-issues-improper-https-forwarding-headers/84745 "2018-04-06T18:04:40Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![cloudunicorn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cloudunicorn/32/88774_2.png) [@cloudunicorn](https://meta.discourse.org/u/cloudunicorn)\ **Post date:** [April 6, 2018, 6:04pm UTC](https://meta.discourse.org/t/paid-user-login-issues-improper-https-forwarding-headers/84745/1 "2018-04-06T18:04:40Z")
**What would you like done?** Been having regular login issues for my users. I mentioned here: > [@Users can't sign in due to 403 error](https://meta.discourse.org/t/users-cant-sign-in-due-to-403-error/56449/9): > > My users just started seeing “403 Unknown Error” when trying to log in. I followed these instructions - but I’m now getting an error in the admin settings: " \* Your website is using SSL. But [force\_https](https://movermaker.com/admin/site\_settings/category/all\_results?filter=force\_https) is not yet enabled in your site settings." I am using the Digital Ocean app setup with nothing custom, and ‘v2.0.0.beta2 +170’. Is this because I’m using a beta version? The issue seems clear to responders but not sure on a solution. As mentioned there I executed the suggested changes and it hasn’t solved anything. Would like someone to fix this + outline how it was done so I don’t run into similar issues in the future. Using Digital Ocean Ubuntu Discourse 2.0.20170531 on 16.04, behind Cloudflare. **When do you need it done?** ASAP, this has been a real problem for our early community. **What is your budget, in $ USD that you can offer for this task?** Not sure, hoping this is a pretty quick fix. Will pay for the time spent. Estimates welcome! --- _[View the full topic](https://meta.discourse.org/t/paid-user-login-issues-improper-https-forwarding-headers/84745)._