Ralf, Stefan, All,
I’ve been working to get push working on the 23.1 dev install on Archlinux. I’ve stumbled through the egroupware/swoolepush/README.md and set up a proxy on the server using Apache with the following (Adapted for the Archlinux document root) following under “To install EGroupwares push server for a regular webserver running on the host follow these instructions:”
## eGroupWare 23.1 push
<Location /egroupware/push>
Require all granted
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /srv/http/htdocs/(.*) ws://localhost:9501/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule /srv/http/htdocs/(.*) http://localhost:9501/$1 [P,L]
ProxyPreserveHost On
ProxyPassReverse http://localhost:9501
</Location>
I’m encouraged, because clients do attempt to connect, but currently are refused. I was unclear on the necessity of the docker --rm command in the README.md since docker isn’t involved here. The errors generated are:
[Sun Nov 03 17:36:40.126899 2024] [proxy:error] [pid 16726:tid 16726] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:9501 (localhost:9501) failed
[Sun Nov 03 17:36:40.126966 2024] [proxy_wstunnel:error] [pid 16726:tid 16726] [client 192.168.6.104:58976] AH02452: failed to make connection to backend: localhost
The .104 IP is my laptop.
I may just be misunderstanding and this may not be possible, because I’m not aware of anything at port 9501 that could handle the request absent it being something that eGroupware does.
I thought I would run it by you guys to see if I’m just wasting my time, or if there is something I missed that should make this work? Thank you and have a good week.
