-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Federation shares ignore server ports #11667
Comments
Checked them, I don't think they are related. |
Update: Further tests confirmed it must be the port being ignored:
So the only constellation where it fails is between A and B (any direction, as described in the initial post), with B having the web server reachable via a non-standard port only from outside. |
Last update: Upgrading A to Nextcloud 13 solved the issue. Now all 3 instances can share between another. Sidenote: B still runs on NC 12 (using one app that's no longer available with 13+, still looking for a replacement to that). C even is only NC 10 (cannot upgrade further before upgrading the entire box, as it still only offers PHP 5.4). |
I run two Nextcloud instances, one of them (let's call it "B") is using a custom server port as 443 is already in use by a different machine behind the same public IP, the other ("A") is reachable via standard port (443). Both servers have the federation app activated, and its counterpart added as "trusted" (with the port specified for B when adding it to A, like
https://example.com:8843/nextcloud
).When I share something from B to A, the notification pops up on A and I can accept – but the share never shows up. The other way around, I can't even accept it.
No Nextcloud log entries on B in either case – but on A I see:
which suggests the port is being ignored (as I don't see it mentioned), and a connection on the default port (443) is tried – with the result of getting the certificate from the wrong server (which, finding no suitable server name via SNI, defaults to a self-signed cert).
Side-note: I cannot find a corresponding Apache log entry on B. The only 3 entries I find are from "Nextcloud Crawler": 1 to
ocs-provider/
, 1 toocs/v2.php/cloud/shares?format=json
, and 1 tostatus.php
– no PROPFIND.Steps to reproduce
Expected behaviour
I can accept the share on either side, and access its contents.
Actual behaviour
Share cannot be accepted on B – and doesn't show after being accepted on A
Server configuration
Operating system:
Debian 9.4
Web server:
Apache 2.4
Database:
MariaDB
PHP version:
7.0.27
Nextcloud version: (see Nextcloud admin page)
12.0.7.1
Updated from an older Nextcloud/ownCloud or fresh install:
Updated from previous versions, reaching back to 9.
Where did you install Nextcloud from:
Download from nextcloud website
Signing status:
Signing status
No errors have been found.List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
No
Are you using encryption: yes/no
No
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
No
LDAP configuration (delete this part if not used)
None
Client configuration
Browser:
Firefox
Operating system:
Linux Mint
Logs
Web server error log
As written above: No matching entries here.
Nextcloud log (data/nextcloud.log)
Nextcloud log
{"reqId":"W7p6ZH8AAQEAACknWdQAAAAN","level":3,"time":"2018-10-07T21:28:06+00:00","remoteAddr":"1.2.3.4","user":"myUser","app":"files_external","method":"PR OPFIND","url":"\/nextcloud\/remote.php\/webdav\/","message":"SSL certificate problem: self signed certificate in certificate chain","userAgent":"Mozilla\/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko\/20100101 Firefox\/55.0","version":"12.0.7.1"}Browser log
Browser log
The text was updated successfully, but these errors were encountered: