Client stuck (Assets Failed) / Nitro AtomPack
- Thread starter Amin1
- Start date
Puffin
Member
- Mar 17, 2018
- 451
- 404
404 Error means not found, in this case it could be one of two things-
Your path to your assets in renderer-config is incorrect, or you forgot to add .NITRO as a MIME Type
Your path to your assets in renderer-config is incorrect, or you forgot to add .NITRO as a MIME Type
To allow us to connect to our client, later on, we must tell IIS to allow ".nitro" file types otherwise, IIS won't know to handle those, resulting in us not being able to connect to the client.
To add the ".nitro" MIME type, all we have to do is open up our "Internet Information Services" application, expand the section just beneath the "Start Page" and double click on the "MIME Types" module:
Once you have double-clicked on the "MIME Types" module, you should be able to click "Add..." in the right top corner. when "Add..." has been clicked, a new popup should appear asking for a "Filename extension:" and a "MIME type:".
In the "File name extension:" field add ".nitro" and inside the "MIME type:" field add: "application/octet-stream" and click "OK".
Here's a GIF on how to do it:You must be registered for see links
. I forgot this .nitro thing.
boz
don daddy
- Mar 23, 2021
- 223
- 105
The console tells you all you need to know. Your assets are not found, click the link and open in a new tab, if it shows 404 then edit you me renderer-config to the correct url.
Puffin
Member
- Mar 17, 2018
- 451
- 404
I thought switching to ws for localhost rather than wss solved this as I stated above ?
Also if you're getting a 404 error for assets then they aren't linked correctly.
404 is a NOT FOUND error. Since we solved the MIME type issue, it's not that.... If it can't find them now then it isn't correctly linked.
