Cannot update users remotely

[doonze 30]

So I recently was updating a new users settings. I realized if I'm connected remotely (still on my home network, but connected to my public reverse proxy, AKA https://mydomain.net) when I go to save changes to users a circle starts spinning on the screen, but the changes never save. If I login local, AKA to the local server IP address, there are no problems saving. I'm pretty sure I was able to CREATE the user from https://mydomain.net and update their password, I just can't make changes to their profile or accesses. Any ideas?

[Luke 40104]

HI, please attach the emby server log from when the problem occurred. Thanks.

[doonze 30]

Sorry @Lukesometimes I don't get notifications from the forum. And then I forgot all about this issue, so didn't check back. Here's a screen shot:

 

This was for my user jaymes, I unchecked the three boxes you see unchecked in the screenshot. Then I hit save. That circle started spinning and didn't stop after waiting for a minute or more. I hit refresh on the page, and the settings were not changed. This is "remotely" from my https://emby.xxxxxx.net instance behind my apache reverse proxy. Works fine if I go to the LAN address. Of note, it just seems to be the profile page. I had no problem making changes to jaymes on the access page. I tried the changes at around 4:30 AM. I've attached my logs. The lines in question are all the last lines. I do see a 500 response.

T

embyserver.txt

Edited October 15, 2023 by doonze

[doonze 30]

Of interest, here is my Apache config file, or the relevant parts at least. I haven't changed anything here in 5 years. Aside from just changing to localhost. I had my FQDN from the local hosts file in there, but there was no reason for that. So before I posted it changed it to localhost because it gave out too much info. Did test again, because apache is weird. But it still doesn't work.

     DocumentRoot /var/www/html/
     Protocols h2 http/1.1
     LogLevel warn
     ServerSignature Off

    ProxyRequests off
    ProxyPreserveHost on
    SSLProxyEngine on

    <Directory /var/www/html/>

        AllowOverride AuthConfig
        RewriteEngine on
        RewriteCond %{LA-U:REMOTE_USER} !^$
        redirect / /emby

   </Directory>
 
     ProxyPass        /socket ws://localhost:8096/socket
     ProxyPassReverse /socket ws://localhost:8096/socket

     ProxyPass        / http://localhost:8096/emby/
     ProxyPassReverse / http://localhost:8096/emby/

 

 

Edited October 15, 2023 by doonze

[doonze 30]

Well, I fixed this myself. I got the idea to use the F12 devtools to see what was going on. I noticed that local ws worked, but on remote (https//mydomain.net) wss was getting a connection error on the console. I remember this was something I'd noticed long ago, and tried to fix, without luck. Everything worked (or so I thought) so I just gave up. I didn't KNOW if this was my problem, but darn it, I don't like errors in my webserver.  

After a few hours with Google, and the forum here as well, I finally got it working. And lo-and-behold.... Saving on the profile page is working now. I did a massive overhaul of my virtual host in apache.

BTW: 

RewriteRule ^/?(.*)$ ws://localhost:8096/$1 [P,L]

that is mentioned here in other forum posts, and on every WS/WSS page I could find, would NOT work for me. For whatever reasons. 

My working config:

<VirtualHost *:443>
     SSLEngine On

     ServerAdmin admin@dddddd.xxx
     ServerName emby.dddddd.xxx
     DocumentRoot /var/www/html/
     Protocols h2 h2c http/1.1
     LogLevel warn
     ErrorLog ${APACHE_LOG_DIR}/emby.error.log
	 CustomLog ${APACHE_LOG_DIR}/emby.access.log combined
     ServerSignature Off

     ProxyRequests off
     ProxyPreserveHost on
     SSLProxyEngine on

	 RewriteEngine on
	 RewriteCond ${HTTP:Connection} upgrade [NC]
	 RewriteCond ${HTTP:Upgrade} websocket [NC]

     ProxyPass /embywebsocket ws://localhost:8096/
     ProxyPassReverse /embywebsocket/ ws://localhost:8096/

     ProxyPass        / http://localhost:8096/
     ProxyPassReverse / http://localhost:8096/  
   
     <IfModule mod_headers.c>
         Header always set Strict-Transport-Security "max-age=15768000; includeSubDomains; preload"
     </IfModule>
     
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/dddddd.xxxt/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/dddddd.xxx/privkey.pem
</VirtualHost>

No more errors on WSS in the browser devtools, and I can edit uses just like on local.

Edited October 15, 2023 by doonze

[Luke 40104]

Thanks for following up !