Unable to verify when using nginx reverse proxy about sshwifty

[nirui]

I've changed how password is authenticated in the last version, which includes modification for both frontend(the web interface) and the backend code.

Maybe the web browser is still using cached old frontend program from the previous version.

Can you reload the page (via Ctrl+F5 or Ctrl+Shift+R to force cache reload) to see if it comes back to normal?

[XZB-1248]

I've changed how password is authenticated in the last version, which includes modification for both frontend(the web interface) and the backend code.

Maybe the web browser is still using cached old frontend program from the previous version.

Can you reload the page (via Ctrl+F5 or Ctrl+Shift+R to force cache reload) to see if it comes back to normal?

Of course I tried that.
Before I open this issue, I even tried to disable cache in dev tools and reload in InPrivate window.
But the error was still there, it doesn't work at all.

[nirui]

That's weird. Based on the screenshot, your web browser is still trying to load the old frontend assets.

I knew that because I changed how the name of the assets is generated in the lastest version. The new version does not include the number prefix (0.xxxxx.js, 1.xxxxx.js etc) in their names.

I think the Nginx or some other (CDN) servers down the line might have cached the / file (The homepage file).

So, to begin, can you take a look at cache related settings? Maybe try to manually release the cache for /.

[XZB-1248]

That's weird. Based on the screenshot, your web browser is still trying to load the old frontend assets.

I knew that because I changed how the name of the assets is generated in the lastest version. The new version does not include the number prefix (0.xxxxx.js, 1.xxxxx.js etc) in their names.

I think the Nginx or some other (CDN) servers down the line might have cached the / file (The homepage file).

So, to begin, can you take a look at cache related settings? Maybe try to manually release the cache for /.

Ohhhh. It works!!!
I added "proxy_cache off;"

Thx for Ur help😎😎😎

[nirui]

Glad that I've helped.

I just had to change the authentication method so I can deploy Sshwifty on my cluster without giving myself a headache. Sorry for the inconvenience and frustration 😆

[XZB-1248]

Glad that I've helped.

I just have to change the authentication method so I can deploy Sshwifty on my cluster without giving myself a headache. Sorry for the inconvenience and frustration 😆

😂😂😂That doesn't matter, it didn't waste time.
Sooner or later, there will be similar problems.