You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed in my developer console that after using a different (public domain, e.g. mycloud.example.com), the JS worker is trying to connect to the default domain from setup. The error I'm receiving:
Firefox can’t establish a connection to the server at wss://nextcloudpi/push/ws. notifications-vendors-node_modules_nextcloud_initial-state_dist_index_esm_js-node_modules_nextcloud_moment_-4efa53.js:2:54060
I guess there should be a dynamic change to a different trusted_domains for wss protocol. But I guess that must be fixed in config.php somewhere else than that directive?
System information
NextcloudPi diagnostics
NextcloudPi version v1.52.1
NextcloudPi image NextCloudPi_RaspberryPi_v1.52.0.img
OS Debian GNU/Linux 11. 5.15.61-v8+ (aarch64)
automount yes
USB devices sda
datadir /media/myCloudDrive/ncdata/data
data in SD no
data filesystem btrfs
data disk usage 185G/1.9T
rootfs usage 5.7G/59G
swapfile /var/swap
dbdir /var/lib/mysql
Nextcloud check ok
Nextcloud version 26.0.1.1
HTTPD service up
PHP service up
MariaDB service up
Redis service up
HPB service up
Postfix service up
Internet check ok
Public IPv4 ***REMOVED SENSITIVE VALUE***
Public IPv6 ***REMOVED SENSITIVE VALUE***
Port 80 open
Port 443 open
IP ***REMOVED SENSITIVE VALUE***
Gateway ***REMOVED SENSITIVE VALUE***
Interface eth0
Certificates ***REMOVED SENSITIVE VALUE***
NAT loopback yes
Uptime 36days
[Sat Aug 26 00:00:00.767978 2023] [ssl:warn] [pid 612087:tid 548130223168] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 26 00:00:00.773054 2023] [mpm_event:notice] [pid 612087:tid 548130223168] AH00489: Apache/2.4.56 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Sat Aug 26 00:00:00.773094 2023] [core:notice] [pid 612087:tid 548130223168] AH00094: Command line: '/usr/sbin/apache2'
[Sat Aug 26 14:55:18.403174 2023] [mpm_event:notice] [pid 612087:tid 548130223168] AH00492: caught SIGWINCH, shutting down gracefully
[Sat Aug 26 14:55:18.529829 2023] [ssl:warn] [pid 2179534:tid 547895940160] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 26 14:55:18.558657 2023] [ssl:warn] [pid 2179538:tid 547895940160] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 26 14:55:18.563592 2023] [mpm_event:notice] [pid 2179538:tid 547895940160] AH00489: Apache/2.4.56 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Sat Aug 26 14:55:18.563817 2023] [core:notice] [pid 2179538:tid 547895940160] AH00094: Command line: '/usr/sbin/apache2'
[Sat Aug 26 14:59:37.180332 2023] [mpm_event:notice] [pid 2179538:tid 547895940160] AH00492: caught SIGWINCH, shutting down gracefully
[Sat Aug 26 14:59:37.288084 2023] [ssl:warn] [pid 2179720:tid 548272579648] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 26 14:59:37.312269 2023] [ssl:warn] [pid 2179722:tid 548272579648] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Sat Aug 26 14:59:37.321590 2023] [mpm_event:notice] [pid 2179722:tid 548272579648] AH00489: Apache/2.4.56 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Sat Aug 26 14:59:37.321737 2023] [core:notice] [pid 2179722:tid 548272579648] AH00094: Command line: '/usr/sbin/apache2'
The text was updated successfully, but these errors were encountered:
bozicm
changed the title
Secure web sockets wss still called at the old domain
Secure web sockets still called at the old domain
Aug 26, 2023
I've noticed in my developer console that after using a different (public domain, e.g. mycloud.example.com), the JS worker is trying to connect to the default domain from setup. The error I'm receiving:
I guess there should be a dynamic change to a different
trusted_domains
for wss protocol. But I guess that must be fixed in config.php somewhere else than that directive?System information
NextcloudPi diagnostics
Nextcloud configuration
HTTPd logs
The text was updated successfully, but these errors were encountered: