After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772326 - Please include port number in Sharing>File Sharing
Please include port number in Sharing>File Sharing
Status: RESOLVED DUPLICATE of bug 730444
Product: gnome-control-center
Classification: Core
Component: Sharing
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-10-02 05:30 UTC by Jeremy Bicha
Modified: 2016-10-02 13:15 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22



Description Jeremy Bicha 2016-10-02 05:30:26 UTC
What happened
=============
- I enabled Sharing>Personal File Sharing on a Fedora 24 host (GNOME 3.20).
- I then entered the dav:// link it provided in Nautilus's "Connect to Server" on Ubuntu 16.04 LTS.
- Well, technically, I used my IP address instead of the hostname since my local home network couldn't resolve the hostname

- It didn't connect and gave me this popup "Unhandled error message: HTTP Error: Could not connect: Connection refused"

Workaround
==========
GNOME 3.22 host:
----------------
systemctl status --user gnome-user-share-webdav.service
Look for whatever 5 digit port apache is set to Listen to
Then connect to something like dav://192.168.0.101:35753

GNOME 3.20 host:
----------------
netstat -an | grep "LISTEN "
Look for a 5-digit port number and connect to that like above

Suggested fix
=============
Add the port number to the "File Sharing" window in Settings>Sharing. This should be possible without affecting translations.

The port number apparently changes every time the service is started.
Comment 1 Bastien Nocera 2016-10-02 13:15:00 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 730444 ***