403 error is usually for access issues. Can you confirm if the user is logged in as admin even in that scenario this error is seen?
Also we need to check everyone user's permissions.
Looking at the placement of html in wrong path (The selector is added after forming the html based url)), can you check if you have any custom code that adds a .html to a resource path. Can't recall any ootb service that does this. May be link externalizer.