push server is not receiving redis messages

[Luticus]

I have the redis server set up on a system on my network and nextcloud is configured to use it properly. It's been working a long time and through many version of nextcloud. Still working in NC21 too.

However when I attempt to go through the manual install (the auto install wouldn't work for me either) I get this message when setting the server location: push server is not receiving redis messages

I'm using the Nextcloud config.php file as recommended in the setup guide. Also I'm using an apache2 reverse proxy.

I do see the "redis is configured" message before the error where it tells me it's not receiving redis messages, so I assume that it's seeing the redis configuration.

To be specific my redis server runs on a different box and the redis settings in nextcloud's config.php point to the server:port of the redis server.

The OS is Debian 10

[icewind1991]

can you run the binary with LOG=notify_push=trace environment variable and check the parsed config it outputs.

[mnestor]

Do you have a login app installed like sociallogin?

I have sociallogin installed for auth against keycloak and it appears that the test/cookie url path is causing a login redirect and failing the test for me.

nextcloud_app.1.i6bry5m7bjaw@dock01    | 10.0.9.35 - - [23/Feb/2021:13:56:32 -0500] "GET /push/test/cookie HTTP/1.1" 302 1559 "-" "Nextcloud Server Crawler"
nextcloud_app.1.i6bry5m7bjaw@dock01    | 10.0.9.35 - - [23/Feb/2021:13:56:32 -0500] "GET /login HTTP/1.1" 302 1560 "-" "Nextcloud Server Crawler"
nextcloud_app.1.i6bry5m7bjaw@dock01    | 10.0.9.35 - - [23/Feb/2021:13:56:32 -0500] "GET /apps/sociallogin/custom_oidc/keycloak HTTP/1.1" 302 1789 "-" "Nextcloud Server Crawler"

So it appears we need to go file a bug report with sociallogin?

edit: actually all the test paths. perhaps it needs to have an internal auth token it can use to bypass the auth requirement.

[Luticus]

@icewind1991 Well I see this:
The application panicked (crashed). Message: error binding to 0.0.0.0:80: error creating server listener: Permission denied (os error 13) Which makes sense, low ports need root to bind and you guys have the bin running as www-data I think.

-scratch that, this issue is mitigated with the systemd service setting the port to 7867. When I also set the LOG=notify_push=trace in the systemd service or even manually it doesn't really show much with a journalctl -fu notify_push.service. I checked the output on the file like you suggested and the redis output looks ok.

redis: ConnectionInfo { addr: Tcp("redis.example.com", ), db: 0, username: None, passwd: Some("") }

The port and password appear to be correct, I've obviously redacted them here though.

The log outputs DEBUG [notify_push] src/lib.rs:338: Received test cookie ######### when I attempt to do sudo -u www-data php occ notify_push:setup https://www.example.com/push

@mnestor I don't have sociallogin, but I do use the 2fa apps: Two-Factor TOTP Provider 6.0.0 Two-Factor U2F 6.1.0 Two-Factor Admin Support 3.0.0

I also use LDAP authentication, if that matters

I have noticed that there is an update to the Client Push app, so I'll test with that too and let you know. (issue still occurs on version 0.1.3)

Also food for thought, the directions say to install the notify_push app, which is the app name if you install via occ, but if you go to the gui nextcloud interface it's "Client Push". The directions should probably be updated to clarify that, I only found it because I knew to try it with occ app:install.

[Chartman123]

Sorry for the wrong reference, I had a typo in my first commit message and I can't figure it out how to remove this reference here... 🙈

[icewind1991]

DEBUG [notify_push] src/lib.rs:338: Received test cookie #########

Looks like it is getting the redis message but maybe there is something wrong with communicating that back to the nextcloud app.

0.1.4 adds a bit more info here during the self test

So it appears we need to go file a bug report with sociallogin?

edit: actually all the test paths. perhaps it needs to have an internal auth token it can use to bypass the auth requirement.

Those endpoints are all marked as public so I would say any app adding auth requirements for them is a problem with that app.

[Luticus]

With the newest version I get this: push server is not receiving redis messages (received 1005149735, got 0)

[icewind1991]

@Luticus do you still get a DEBUG [notify_push] src/lib.rs:338: Received test cookie in the notify_push output?

[andreaslutsch]

After removing the nginx reverse proxy block and setting a local NEXTCLOUD_URL variable I also have this issue. The service seems to work, I think, but if I do notify_push:self_test or setup, then I also receive 🗴 push server is not receiving redis messages (received 211886646, got 0). I enabled the trace log and also see DEBUG [notify_push] src/lib.rs:360: Received test cookie 211886646 and also other debug lines like: Received storage update notification for storage 7 and path appdata_ocvey4ezdjce/text/documents/331972

DEBUG [notify_push::storage_mapping] src/storage_mapping.rs:96: querying storage mapping for 7 DEBUG [notify_push] src/lib.rs:360: Received storage update notification for storage 7 and path appdata_ocvey4ezdjce/text/documents DEBUG [notify_push] src/lib.rs:360: Received pre_auth user andreasus

I'm not sure if these mean that notify push works or not. I also updated to 0.1.5

[Luticus]

@icewind1991 I do, even with 0.1.5: DEBUG [notify_push] src/lib.rs:360: Received test cookie 1062812323

[Luticus]

0.1.6 doesn't seem to work either, same error about redis messages.

sudo -u www-data php occ notify_push:setup https://www.example.com/push [sudo] password for user: ✓ redis is configured 🗴 push server is not receiving redis messages (received 506331649, got 0)

[brknkfr]

I had the same problem and changing proxy_set_header Host $http_host; (in my case) to proxy_set_header Host $host; in my nginx config fixed it.

[Luticus]

@brknkfr I'm not sure if that will work for me unfortunately, as my Nextcloud is set up on an Apache server so I guess I need to see if there's something equivalent that I could try.

After looking at the nginx instructions, I get what you were saying. That particular directive you changed doesn't seem to match up with anything on the Apache side. I tried using: ProxyPass /push/ws ws://127.0.0.1:7867/ws ProxyPass /push/ http://127.0.0.1:7867/ ProxyPassReverse /push/ http://127.0.0.1:7867/

and even tried a ProxyPassReverse for the websocket, with no luck

even tried it like this: ProxyPass /push/ws ws://www.mydomain.com:7867/ws ProxyPass /push/ http://www.mydomain.com:7867/ ProxyPassReverse /push/ http://www.mydomain.com:7867/

Also tried it with ProxyPass set to use https instead. When using https is when i get the redis error. When using just http, I get this instead: sudo -u www-data php occ notify_push:setup https://www.mydomain.com/push ✓ redis is configured 🗴 can't connect to push server: Client error: GET https://www.mydomain.com/push/test/cookie resulted in a 404 Not Found response

and if i try like this: sudo -u www-data php occ notify_push:setup http://www.mydomain.com/push ✓ redis is configured 🗴 using unencrypted https for push server is strongly discouraged 🗴 can't connect to push server: Client error: GET http://www.mydomain.com/push/test/cookie resulted in a 404 Not Found response: Not found

you can see that doesn't seem to work either.

[Nick-Git2]

I'm having the same issue using the latest version 1.7:

sudo -u www-data /var/www/nextcloud/occ notify_push:setup https://XXXXX/nextcloud/push ✓ redis is configured 🗴 push server is not receiving redis messages (received 904222169, got 0)

Debugging Log says:

Apr 13 22:58:10 debian systemd[1]: Started Push daemon for Nextcloud clients.

Apr 13 22:58:10 debian notify_push[1552]: [2021-04-13 22:58:10.507747 +02:00] TRACE [notify_push] src/main.rs:42: Running with config: Config { database: AnyConnectOptions(MySql(MySqlConnectOptions { host: "localhost", port: 3306, socket: None, username: "XXXXX", password: Some("XXXXX"), database: Some("XXXXX"), ssl_mode: Preferred, ssl_ca: None, statement_cache_capacity: 100, charset: "utf8mb4", collation: None, log_settings: LogSettings { statements_level: Info, slow_statements_level: Warn, slow_statements_duration: 1s } })), database_prefix: "oc_", redis: [ConnectionInfo { addr: Tcp("localhost", 6379), db: 0, username: None, passwd: None }], nextcloud_url: "https://XXXXX/nextcloud/", metrics_bind: None, log_level: "notify_push=trace", bind: Tcp(0.0.0.0:7867), allow_self_signed: false }

Apr 13 22:58:10 debian notify_push[1552]: [2021-04-13 22:58:10.509237 +02:00] DEBUG [notify_push::storage_mapping] src/storage_mapping.rs:96: querying storage mapping for 1 Apr 13 22:58:10 debian notify_push[1552]: [2021-04-13 22:58:10.579356 +02:00] TRACE [notify_push] src/main.rs:59: Listening on 0.0.0.0:7867 Apr 13 22:58:14 debian notify_push[1552]: [2021-04-13 22:58:14.581417 +02:00] DEBUG [notify_push] src/lib.rs:399: Received test cookie 817484235

I don't know what could be wrong. It seems that everything's up and running and is listening on the right ports

[Luticus]

Just tested 1.7 as well, no luck. issue is exactly the same. I'm thinking there's gotta be some weird config issue I'm missing somewhere, or something. I followed the directions to the letter though, so I'm not sure what it could be.

[icewind1991]

Can you try running curl https://example.com.com/push/test/cookie after running the setup command

[gldhnchn]

Looks like I have the same issue.

$ sudo -u www-data /usr/bin/php -f /var/www/nextcloud/occ notify_push:setup https://example.com
✓ redis is configured
🗴 push server is not receiving redis messages (received 337895478, got 0)

Output in the log

Apr 14 17:54:57 blackhole notify_push[15879]: [2021-04-14 17:54:57.278104 +02:00] TRACE [tokio_util::codec::framed_impl] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-util-0.6.5/src/codec/framed_impl.rs:135: attempting to decode a frame
Apr 14 17:54:57 blackhole notify_push[15879]: [2021-04-14 17:54:57.278139 +02:00] TRACE [tokio_util::codec::framed_impl] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-util-0.6.5/src/codec/framed_impl.rs:138: frame decoded from buffer
Apr 14 17:54:57 blackhole notify_push[15879]: [2021-04-14 17:54:57.278150 +02:00] DEBUG [notify_push] src/lib.rs:399: Received test cookie 337895478
Apr 14 17:54:57 blackhole notify_push[15879]: [2021-04-14 17:54:57.278159 +02:00] TRACE [tokio_util::codec::framed_impl] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-util-0.6.5/src/codec/framed_impl.rs:135: attempting to decode a frame

$ curl -v https://example.com/push/test/cookie
*   Trying 92.116.***.***:443...
* TCP_NODELAY set
* Connected to example.com (92.116.***.***) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=example.com
*  start date: Apr  1 11:20:43 2021 GMT
*  expire date: Jun 30 11:20:43 2021 GMT
*  subjectAltName: host "example.com" matched cert's "example.com"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x559eb1776cb0)
> GET /push/test/cookie HTTP/2
> Host: example.com
> user-agent: curl/7.68.0
> accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200 
< server: nginx
< date: Wed, 14 Apr 2021 15:57:54 GMT
< content-type: text/plain; charset=utf-8
< content-length: 9
< x-frame-options: SAMEORIGIN
< x-robots-tag: none
< referrer-policy: no-referrer
< x-content-type-options: nosniff
< x-download-options: noopen
< x-permitted-cross-domain-policies: none
< x-xss-protection: 1; mode=block
< strict-transport-security: max-age=63072000; includeSubdomains
< cache-control: public, max-age=15778463
< 
* Connection #0 to host example.com left intact
337895478%

output in the log:

Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319472 +02:00] TRACE [mio::poll] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.7.11/src/poll.rs:478: registering event source with poller: token=Token(117440513), interests=READABLE | WRITABLE
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319536 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:140: Conn::read_head 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319553 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:81: parse_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319562 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:81: -> parse_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319569 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:129: Request.parse([Header; 100], [u8; 212]) 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319579 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:138: Request.parse Complete(212) 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319588 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:153: headers: [Header { name: "X-Forwarded-Proto", value: [104, 116, 116, 112, 115] }, Header { name: "Connection", value: [85, 112, 103, 114, 97, 100, 101] }, Header { name: "Host", value: [110, 101, 120, 116, 99, 108, 111, 117, 100, 46, 103, 108, 100, 104, 110, 99, 104, 110, 46, 100, 101] }, Header { name: "X-Forwarded-For", value: [49, 56, 56, 46, 55, 52, 46, 51, 50, 46, 50, 53, 51, 44, 32, 49, 50, 55, 46, 48, 46, 48, 46, 49] }, Header { name: "X-Real-IP", value: [49, 56, 56, 46, 55, 52, 46, 51, 50, 46, 50, 53, 51] }, Header { name: "user-agent", value: [99, 117, 114, 108, 47, 55, 46, 54, 56, 46, 48] }, Header { name: "accept", value: [42, 47, 42] }] 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319618 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:81: <- parse_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319626 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:81: -- parse_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319633 +02:00] DEBUG [hyper::proto::h1::io] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/io.rs:167: parsed 7 headers 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319641 +02:00] DEBUG [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:158: incoming body is empty 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319657 +02:00] TRACE [warp::filters::path] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.1/src/filters/path.rs:212: "ws"?: "test" 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319668 +02:00] TRACE [warp::filters::path] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.1/src/filters/path.rs:212: "test"?: "test" 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319675 +02:00] TRACE [warp::filters::path] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.1/src/filters/path.rs:212: "cookie"?: "cookie" 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319684 +02:00] DEBUG [notify_push] src/lib.rs:249: current test cookie is 337895478
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319699 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:93: encode_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319706 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:93: -> encode_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319713 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:291: Server::encode status=200, body=Some(Known(9)), req_method=Some(GET) 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319724 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:93: <- encode_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319738 +02:00] TRACE [hyper::proto::h1::role] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/role.rs:93: -- encode_headers
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319775 +02:00] DEBUG [hyper::proto::h1::io] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/io.rs:248: flushed 125 bytes 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319790 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:663: flushed({role=server}): State { reading: Init, writing: Init, keep_alive: Idle } 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319871 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:140: Conn::read_head 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319893 +02:00] TRACE [hyper::proto::h1::io] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/io.rs:179: parse eof 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319902 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:868: State::close_read() 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319910 +02:00] DEBUG [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:208: read eof 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319917 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:874: State::close_write() 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319924 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:868: State::close_read() 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319931 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:874: State::close_write() 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319938 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:663: flushed({role=server}): State { reading: Closed, writing: Closed, keep_alive: Disabled } 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319981 +02:00] TRACE [hyper::proto::h1::conn] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/proto/h1/conn.rs:670: shut down IO complete 
Apr 14 17:57:54 blackhole notify_push[15879]: [2021-04-14 17:57:54.319992 +02:00] TRACE [mio::poll] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.7.11/src/poll.rs:609: deregistering event source from poller
Apr 14 17:57:56 blackhole notify_push[15879]: [2021-04-14 17:57:56.148064 +02:00] TRACE [hyper::client::pool] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/client/pool.rs:749: idle interval checking for expired 

systemd unit of notify_push:

[Unit]
Description = Push daemon for Nextcloud clients

[Service]
Environment = PORT=7867
Environment = NEXTCLOUD_URL=https://example.com
Environment = RUST_BACKTRACE=full
Environment = LOG=trace
ExecStart = /var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push /var/www/nextcloud/config/config.php
User=www-data

[Install]
WantedBy = multi-user.target

[Nick-Git2]

$ sudo -u www-data /var/www/nextcloud/occ notify_push:setup https://XXXXX/nextcloud/push ✓ redis is configured 🗴 push server is not receiving redis messages (received 649162221, got 0)

$ sudo curl https://XXXXX/push/test/cookie 649162221

[chrissi55]

I made the step sudo -u www-data /var/www/nextcloud/occ notify_push:setup https://my.domain/push

and it seems working with 0.1.7 either but the question is, is there a parameter / Environment variable for /etc/systemd/system/notify_push.service that let me use a password for redis again. in my nextcloud config.php i commented out the redis pass because i disabled the option in redis because of auth errors setting up notify_push.

Thanks

Environment = REDIS_PASSWORD=....
or
Environment = REDIS_PASS_FILE=.....

are not recognized nor working

[Luticus]

@icewind1991 When I run curl https://example.com/push/test/cookie running the setup command I get no output of any kind, it just returns. If I run it with a -v as in curl -v https://example.com/push/test/cookie I get basically identical output to @gldhnchn

[sirdrakeistda]

Same problem here. I managed the problem by restarting the service sudo systemctl restart notify_push After this I was able to run sudo -u www-data php occ notify_push:setup again without problems (if you haven't done the step press esc and do not run the step). Maybe my reboot was the issue.

[Nick-Git2]

Same problem here. I managed the problem by restarting the service sudo systemctl restart notify_push After this I was able to run sudo -u www-data php occ notify_push:setup again without problems (if you haven't done the step press esc and do not run the step). Maybe my reboot was the issue.

I've just tried your solution but the issue persists.

[Luticus]

I've restarted the service, disabled and reenabled, then started the service, and rebooted the system. None of these things helped.

[Tamsy]

I am struggling with

✓ redis is configured 🗴 push server is not receiving redis messages (received 804108192, got 0)

for three days now on Apache 2.4 on Ubuntu 18.04.5

I have already tried all "solutions" I could find through the internet but unfortunately to no avail. Have given it up for now and hoping there will be a solution (or at least a workaround) to this error anytime soon.

[Tamsy]

I've restarted the service, disabled and reenabled, then started the service, and rebooted the system. None of these things helped.

@Luticus @gldhnchn @Nick-Git2

Do you by any chance run SpiderLabs's ModSecurity with Apache/Nginx on your Nextcloud Hub?

At least with ModSecurity v.2.x on Apache 2.4.48 this seems to be the culprit of the 🗴 push server is not receiving redis messages (received xxxxxxx, got 0) message.

Using the latest Client Push 0.2.0 I switched off (commented out) LoadModule security2_module modules/mod_security2.so restarted Apache, made sure notify_push.service is running and did occ notify_push:setup which showed:

<snip>
Push binary seems to be running already
✓ push server seems to be functioning correctly.
Reverse proxy seems to be configured already
✓ reverse proxy seems to be setup correctly.
  configuration saved

Thereafter I did: occ notify_push:setup https://cloud.ourcloud.com/push which showed:

✓ redis is configured
✓ push server is receiving redis messages
✓ push server can load mount info from database
✓ push server can connect to the Nextcloud server
✓ push server is a trusted proxy
✓ push server is running the same version as the app
  configuration saved

Client Push seems to be running/working now as it should.

If you have Modsecurity running just deactivate it and give it a try.

[gldhnchn]

@Tamsy: No, I'm not using ModSecurity.

But I did a recheck with the new version 0.2.0 and everything is running fine now. Thank you!

[Xitee1]

But I did a recheck with the new version 0.2.0 and everything is running fine now. Thank you!

I have updated to the version 0.2.0 and have restarted notify_push and the system after the update. I still get 🗴 push server is not receiving redis messages (received 412837236, got 0).

Edit: I saw that there is a error message if i type service notify_push status. Failed to setup redis subscription: Failed to connect to redis: Password authentication failed WARN [notify_push] src/lib.rs:379: Redis server disconnected, reconnecting in 1s

[Luticus]

@Tamsy Nope, I am not using that module. Interestingly though I finally managed to get it to work with the automatic setup process when I tried it on the newest version. When I use the manual one I get the same error. There's probably something missing from the manual steps or I did something wrong with the manual ones. I do have it working now though so maybe this can be closed.

[rererecursive]

I was experiencing this issue as well, and the fix for me was to disable/enable the app in Nextcloud: su www-data -s /bin/bash -c "php occ app:disable notify_push" su www-data -s /bin/bash -c "php occ app:enable notify_push"

[mortee]

I have the same problem with v0.4.0 as @Luticus did, I get the 404 error for /push/test/cookie. Also in the log, I see these lines:

TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "ws"?: "" 
TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "test"?: "" 
TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "test"?: "" 
TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "test"?: "" 
TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "test"?: "" 
TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "test"?: "" 
TRACE [warp::filters::path] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filters/path.rs:212: "push"?: "" 
DEBUG [warp::filter::service] /cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.2/src/filter/service.rs:132: rejected: Rejection(NotFound) 

which is supposed to look like this:

TRACE [warp::filters::path] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.1/src/filters/path.rs:212: "ws"?: "test" 
TRACE [warp::filters::path] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.1/src/filters/path.rs:212: "test"?: "test" 
TRACE [warp::filters::path] /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/warp-0.3.1/src/filters/path.rs:212: "cookie"?: "cookie" 
DEBUG [notify_push] src/lib.rs:249: current test cookie is 337895478

So, apparently, for some reason it refuses to even parse the local part of the request URI. I don't even have the option to set it up using the "wizard", since I intend to run it in a separate docker container.

What might be the problem?

[aakerbeere]

I don't know if this is of any help here.

I occasionally get push server is not receiving redis messages when the server is under heavy load, fex. when an OCR task is running. A subsequent call of occ notify_push:self-test runs successfull.