Unity WebGL can't find my addressables

To speed up my unity webgl initial load time, I’m attempting to make some of my scenes addressable to load later. Below is the code I used for one of the scenes:

AsyncOperationHandle<SceneInstance> loadHandle;
    private void LoadWords()
    {
        loadHandle = Addressables.LoadSceneAsync("wordsLabel", LoadSceneMode.Single);
    }
    void OnDestroy()
    {
        Addressables.UnloadSceneAsync(loadHandle);
    }

I put the scene in a group and gave that group a label of “wordsLabel”.
When I run it on unity’s editor, it all works fine, but when I build it to a webgl (using clean build) and then upload to my server and run it, it shows this error when I click the button that triggers the function “LoadWords”:

HBAMBuild.framework.js.gz:10 RemoteProviderException : Unable to load asset bundle from : [url to my addressable bundle named words_scenes_all_57bce6880117c37ce9125333b1ab0c4a.bundle]
UnityWebRequest result : ProtocolError : HTTP/1.1 404 Not Found
ResponseCode : 404, Method : GET
url : [url to my addressable bundle named words_scenes_all_57bce6880117c37ce9125333b1ab0c4a.bundle]

The parts in bracketts were the url to my addressables which I verified are in my webgl in streamingAssets->aa->addressablesLink ->WebGL

Any idea what I’m missing?

Are you sure the path on the webserver matches the url not found in game? As in its not just say /somefolder/filehere. But the full http://myserver/game/whatever… ?

The url in the bracketts in the error does start with https:// and my website and is the full url to the .bundle. It’s the direct link. Is there some place else that I should check for that?

depending what the webserver is, (windows or not) it could be a disagreement of casing, so “path” vs “Path” etc… checking on the web server as the exact pathing it is looking for, try downloading the file direct with your browser, check your weblogs as to what the server sees, it may show a bit more hints as to what is wrong.

I figured it out. Apparently, clearing the cache and deleting site data isn’t enough to truly clear the cache. I had to also exit chrome. Now it is able to find it.

wow, that is a bit odd, but well done