Skip to content
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

[3.2.4/3.3.0RC] Sharing broken #3014

Closed
AndyScherzinger opened this issue Sep 11, 2018 · 12 comments
Closed

[3.2.4/3.3.0RC] Sharing broken #3014

AndyScherzinger opened this issue Sep 11, 2018 · 12 comments
Labels
bug needs info Waiting for info from user(s). Issues with this label will auto-stale. stale

Comments

@AndyScherzinger
Copy link
Member

AndyScherzinger commented Sep 11, 2018

When I share a file with an Nc user of the same instance (probably the same for any other kind of sharing) it fails with the corresponding snackbar while the share is actually created when checking the webUI.

The reason for this: The server for me Nc14 / for a user in the forum Nc 13 (https://help.nextcloud.com/t/sharing-not-possible-teilen-nicht-moglich/36636/6) is replying with the result code 35 with translates to the ordinal value 35-> SHARE_FORBIDDEN and the mData value Connection could not be established with host 127.0.0.1 [Connection refused #111]. This might be a server (configuration issue) or a client side change to the interpretation of the server response, that I don't know :/

Android 7/8
Client 3.2.4 and latest master

share

@AndyScherzinger AndyScherzinger added bug needs info Waiting for info from user(s). Issues with this label will auto-stale. labels Sep 11, 2018
@AndyScherzinger
Copy link
Member Author

Also cc @nextcloud/server-triage to check if this might be server related

@nextcloud-android-bot

This comment has been minimized.

@tobiasKaminsky
Copy link
Member

  • emulator -> local dev server --> NOT working
  • 3.3.0 RC2 on real phone -> NC14 productive server -> working

@AndyScherzinger
Copy link
Member Author

The connection could not be established error message is sent by the server. I also saw this error for sharing in the web UI of 14.0.0 RC1 but it vanished with the stable (didn't check RC2 of Nc14).

@tobiasKaminsky Is your local server http and your productive server https? Just asking since my productive server is http!

@tobiasKaminsky
Copy link
Member

Yes:
https on productive
http on local machine

--> Testet with latest master on emulator and productive server -> working

@AndyScherzinger
Copy link
Member Author

AndyScherzinger commented Sep 12, 2018

--> Testet with latest master on emulator and productive server -> working

Well, I guess it might be related to https while that would be quite a bug and "lease use https" shouldn't be the workaround/solution ;) Especially since for me the share is created on the server, for Mel on the forum the share isn't created (13.0.6)

@tobiasKaminsky
Copy link
Member

Let us wait on server input for this…

@nickvergessen
Copy link
Member

Connection could not be established with host is from our 3rd party lib which we use to send emails.

I guess this shouldn't break sharing though (only if you do a share by mail)

@AndyScherzinger
Copy link
Member Author

I did a share by user (from user A to user B within the same server)

@burner-
Copy link

burner- commented Sep 13, 2018

I install new vm with ubuntu 18.04. Then I installed nextcloud with this procedure https://github.com/nextcloud/vm
I access that server with windows machine with google chrome and I can confirm that I hit to this same problem. Share will do false positive error message each time.

@tensberg
Copy link

Connection could not be established with host is from our 3rd party lib which we use to send emails.
I guess this shouldn't break sharing though (only if you do a share by mail)

At least for me the problem really was that I had no mailserver configured in my Nextcloud test installation. Configuring one fixed the sharing error.

Apparently Nextcloud 14 always sends a mail to the persons you're sharing with, see nextcloud/server#11216

@stale
Copy link

stale bot commented May 9, 2019

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@stale stale bot added the stale label May 9, 2019
@stale stale bot closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs info Waiting for info from user(s). Issues with this label will auto-stale. stale
Projects
None yet
Development

No branches or pull requests

6 participants