I'm wondering if someone would be kind enough to offer a little help. I'm very new to using Umbraco, but it seems pretty decent and I'm looking to take the master class soon. But, I'm having issues in production.
Locally, the site works, as soon as it's published however, I cannot access the backend. I've read plenty of others who have experienced the same, but all versions relate to v7. I'm currently on v8.12.1.
Having investigated as far as I can, I'm now at the point I could do with a hand.
Things I've tried:
Clearing cookies
Making sure all files are included in the project when publishing
Making sure the relevant permissions are applied to the site folders
Clearing the TEMP folder
Trying Incognitio mode
Checking server time is correct
Making sure no cookie blocking software is running
Incrementing the ClientDependency number
Disabling any HTTPS re-write rules
Turning on debug mode
There's possibly more that I've tried, but it's been a long few days trying to get into the backend.
What I have found is that when I'm logging in locally (still using https) I can see 4 cookies are created when logged in successfully. Attempting to login to production sees just 2 cookies, with production not generating the cookies UMBUCONTEXT or UMBUPDCHK.
There's also a number of failed calls in the console for 401's and "No URL Found for API Name XXX".
What's interesting is, using an iPad or iPhone, I can login just fine. Using any other non iOS device, even on computers that have never visited the site result in the same error.
The main site itself operates just fine.
I have created and deployed 3 separate websites onto the server, all with the same outcome, the main site works, backend does not.
For reference, the first site is a ready for client / fully developed site. The 2nd is a completely blank / fresh Umbraco install, the 3rd is also a fresh install, but with the starter template installed. All have the same issue.
I'm leaning towards thinking it's something server related, but I can't quite figure out what. The IIS App Pool is setup correctly, has all the required permissions and the correct frameworks are installed.
I've attached some screenshots in the hope that someone can assist. I would very much like to embrace Umbraco, but I see plenty of posts with people having issues for something that should "just work".
I spotted a similar issue to mine in that if there's no root node set for a user it may not login. However I've set that, and created a new user and still the same issue persists, anyone offer any advice? - Client site ready to go live, just can't login to the backend
For anyone interested, I span up a new VM instance of Server 2019, copied the same roles / features as my current server and published my vanilla test site to the new server and everything logged in just fine. I installed any pending windows updates on the new server, and the site failed to login leading me to believe it's update related.
I couldn't quite get to find which update was causing the issue specifically, but then thought I would re-try the updates, restarted the server (wasn't prompting for it) then it worked again, so I followed the same process of rebooting the original server and all is well again and I can login.
Still no idea what the issue was, but for now it's resolved.
Cannot Login to backend when published
Hi All,
I'm wondering if someone would be kind enough to offer a little help. I'm very new to using Umbraco, but it seems pretty decent and I'm looking to take the master class soon. But, I'm having issues in production.
Locally, the site works, as soon as it's published however, I cannot access the backend. I've read plenty of others who have experienced the same, but all versions relate to v7. I'm currently on v8.12.1.
Having investigated as far as I can, I'm now at the point I could do with a hand.
Things I've tried:
There's possibly more that I've tried, but it's been a long few days trying to get into the backend.
What I have found is that when I'm logging in locally (still using https) I can see 4 cookies are created when logged in successfully. Attempting to login to production sees just 2 cookies, with production not generating the cookies UMBUCONTEXT or UMBUPDCHK.
There's also a number of failed calls in the console for 401's and "No URL Found for API Name XXX".
What's interesting is, using an iPad or iPhone, I can login just fine. Using any other non iOS device, even on computers that have never visited the site result in the same error.
The main site itself operates just fine.
I have created and deployed 3 separate websites onto the server, all with the same outcome, the main site works, backend does not.
For reference, the first site is a ready for client / fully developed site. The 2nd is a completely blank / fresh Umbraco install, the 3rd is also a fresh install, but with the starter template installed. All have the same issue.
I'm leaning towards thinking it's something server related, but I can't quite figure out what. The IIS App Pool is setup correctly, has all the required permissions and the correct frameworks are installed.
I've attached some screenshots in the hope that someone can assist. I would very much like to embrace Umbraco, but I see plenty of posts with people having issues for something that should "just work".
Thanks
Lee
I spotted a similar issue to mine in that if there's no root node set for a user it may not login. However I've set that, and created a new user and still the same issue persists, anyone offer any advice? - Client site ready to go live, just can't login to the backend
For anyone interested, I span up a new VM instance of Server 2019, copied the same roles / features as my current server and published my vanilla test site to the new server and everything logged in just fine. I installed any pending windows updates on the new server, and the site failed to login leading me to believe it's update related.
I couldn't quite get to find which update was causing the issue specifically, but then thought I would re-try the updates, restarted the server (wasn't prompting for it) then it worked again, so I followed the same process of rebooting the original server and all is well again and I can login.
Still no idea what the issue was, but for now it's resolved.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.