Use high performance backend: access refused

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 31.0.4):
    • replace me
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 22.04
  • Web server and version (e.g, Apache 2.4.25):
    • replace me
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • replace me
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • after I tried to modify the system to use hpb
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • docker
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no, ust nginx reverse proxy

Summary of the issue you are facing:

I followed the docu here and here to use the high performance backend in a docker container. Started container as described and configured the nginx-reverse-proxy as in the pictures.
I can curl the localhost, so hpb ist running so far,

$ curl http://localhost:8181/api/v1/welcome
{"nextcloud-spreed-signaling":"Welcome","version":"2.0.2~docker"}

but I get errors trying to reach it by its docker ip

curl -i http://172.17.0.2/standalone-signaling/api/v1/welcome
curl: (7) Failed to connect to 172.17.0.2 port 80 after 0 ms: Connection refused

or externally.

~$ curl -i https://signal.bardhome.de/standalone-signaling/api/v1/welcome
HTTP/2 502
server: openresty
date: Mon, 05 May 2025 12:57:40 GMT
content-type: text/html
content-length: 154

<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>openresty</center>
</body>
</html>

The logs tell me:
hub.go:264: No trusted proxies configured, only allowing for [127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16]
How can I configure it to accept the connections properly?

I want to use hpb in nextcloud

Steps to replicate it (hint: details matter!):

  1. Start the docker container for hpb

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

see above, no log from nextcloud but from hpb

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

not related to browser

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

not relevant, this is about hpb

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

not relevant

Apps

The output of occ app:list (if possible).

not relevant

Hi,
I also have the same problem with my HPB server installed on a Ubuntu 22.04 vm in self hosting mode. Nextcloud version 31.0.4 was also installed and configured in self hosting mode. I get the following error, similar to yours.

Citazione
ClientException
Client error: POST xxxxxx/standalone-signaling/api/v1/room/koy68k35 resulted in a 403 Forbidden response: Authentication check failed

I saw this topic is very popular lately and so I imagine it is a problem for almost everyone.
Although what you found does not occur on all Nextcloud installations.

Follow and watch this case it could be useful for you, unfortunately, in my case it didn’t work.

I’m happy if someone more experienced than us can help us solve it.

see High Performance Backend for Talk on Nextcloud with Docker and try creating a new secretpasswordkey (min. 24 chars, better 32 chars) for each service!

  • replace secretpasswordkey in docker stack and restart the docker pulling the image.
  • replace secretpasswordkey in your nextcloud Talk config

Thanks for your reply.

My installation is self hosting and therefore I would need to understand how to execute these commands on my vm

Thanks, but it did not help.

I can do

curl http://nextcloud

inside of my nginx-proxy-manager docker container.
Also

curl http://homeassitant:8123

gives me some valid output of http code.

But

curl http://nextcloud-talk-hpb:8181

leads to
curl: (7) Failed to connect to nextcloud-talk-hpb port 8181 after 1 ms: Couldn’t connect to server

Docker network inspect nextcloudpi

tells me they are all in the same network.

This is the docker logs nextcloud-alk-hpb:

main.go:268: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 1s
[WARN] No Unix Sockets server started, giving up...
[WARN] The 'janus.transport.pfunix' plugin could not be initialized
mcu_common.go:110: Maximum bandwidth 1048576 bits/sec per publishing stream
mcu_common.go:117: Maximum bandwidth 2097152 bits/sec per screensharing stream
mcu_janus.go:161: Using a timeout of 10s for MCU requests
mcu_janus.go:342: Connected to Janus WebRTC Server 1.3.1 by Meetecho s.r.l.
mcu_janus.go:350: Found JANUS VideoRoom plugin 0.0.10 by Meetecho s.r.l.
mcu_janus.go:355: Data channels are supported
mcu_janus.go:359: Full-Trickle is enabled
mcu_janus.go:366: Created Janus session 8476051213289583
mcu_janus.go:373: Created Janus handle 5890333230677917
main.go:303: Using janus MCU
hub.go:411: Using a timeout of 10s for MCU requests
backend_server.go:114: No IPs configured for the stats endpoint, only allowing access from 127.0.0.1
main.go:384: Listening on 0.0.0.0:8081

Two things:

main.go:268: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 1s

I have no clue what that means.
And I guess I need to allow some IPs or something otherwise reverse proxy cannot access the container.