Umbraco BackOffice not loading
# help-with-umbraco
j
Hi all! Thanks for reading, the back office for my umbraco solution is not loading and currently looks like the screenshot, the other screenshot is my console. I have a feeling it's something to do with these console errors. Has anyone come across this before? This is a deployed environment. Thanks
a
How did you deploy, did you do a 'dotnet publish' and published those files ?
Definitly has something to do with the console errors 😉
j
elastic beanstalk, so very managed deployment. I imagine it was something similar to dotnet publish
any ideas?
a
I personally have no experience with it, when you check the publsihed files, do you have a umbraco folder with all its contents ?
j
i do! Seems to have all the required js for the backoffice
i've checked the accuracy of the server time, cors, the iis server has full control over the web app etc
So i'm also getting this error /umbraco/Application?umb__rnd=482d8f7c3bbd2e7c8d56fe7a56870c75031815bd unable to load script source
by the way, the backoffice works perfectly in local dev env
a
Yea it seems like none of the files can be loaded for the backoffice, but the question is why
You dont have other console errors where the scripts are blocked or something ?
m
Do you have a CSP in place?
j
no - no content security policy as of right now, made sure to troubleshoot
and no - no other console errors, just blocked scripts
very confusing!
have changed the deployment to dev and still not working
no obvious diff between local and deployed version
the main problem seems to be the angular.js isn't loading at all
could not load content for XXXX/umbraco/lib/angular/angular.js (HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE)
a
Yea tthat means it cant find the files.. Are you sure the file is there in that location, physically ?
h
If the files do exist, check the folder permissions
m
those files will come from the razor class library/embedded resources in core, so might not be physically present?
a
He could try opening one of the files directly (just navigate in your browser to the specfied file), if it doesnt open, it's probably a publish/hosting issue
j
Hi guys, i fixed it by changing the environment variables in elastic beanstalk
p
@User May I suggest “friends” instead of "guys"? We use gender inclusive language in this Discord. 😀
j
no idea why they work fine in the staging environment and not production, but nice accidental security feature?
this was also an issue, the files weren't physically present when it was running with debug=false for some reason
changing debug=true seemed to make it work but definitely not a satisfying result
13 Views