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

Using the hosted edition on non-default port #137

Closed
manust opened this Issue Oct 27, 2014 · 6 comments

Comments

Projects
None yet
2 participants
@manust

manust commented Oct 27, 2014

Hi,
I'm trying to synch the hosted version with ownCloud on a different port, both tools are in the same root directory.
it does work when using 443 (no port in the url then) but when using another port, impossible for TagSpaces to read the ownCloud webdav directory.
I tried using the full URL location path including port without success
the browser can browse the ownCloud webdav URL without any problem

@uggrock

This comment has been minimized.

Show comment
Hide comment
@uggrock

uggrock Oct 28, 2014

Member

Hi,

owncloud and tagspaces have to be installed on the same host and should use the same port. If this is not working, there is probably a bug ... Please notify me in this case.

cheers,
Ilian

Member

uggrock commented Oct 28, 2014

Hi,

owncloud and tagspaces have to be installed on the same host and should use the same port. If this is not working, there is probably a bug ... Please notify me in this case.

cheers,
Ilian

@manust

This comment has been minimized.

Show comment
Hide comment
@manust

manust Oct 28, 2014

Hi,
thanks for your answer
they are on the same host, same webserver, each one in its own directory (/var/www/html/tagspaces and /var/www/html/owncloud, /var/www/html/ being root)

manust commented Oct 28, 2014

Hi,
thanks for your answer
they are on the same host, same webserver, each one in its own directory (/var/www/html/tagspaces and /var/www/html/owncloud, /var/www/html/ being root)

@uggrock

This comment has been minimized.

Show comment
Hide comment
@uggrock

uggrock Oct 29, 2014

Member

How about the port, is it the same for both applications?

Member

uggrock commented Oct 29, 2014

How about the port, is it the same for both applications?

@manust

This comment has been minimized.

Show comment
Hide comment
@manust

manust Oct 29, 2014

Yes exact same port

manust commented Oct 29, 2014

Yes exact same port

@uggrock

This comment has been minimized.

Show comment
Hide comment
@uggrock

uggrock Oct 31, 2014

Member

Ok, issue reproduced and fixed for the next release.
You can fix it yourself be changing location.host to location.hostname in the connectDav function of web.api.js

Member

uggrock commented Oct 31, 2014

Ok, issue reproduced and fixed for the next release.
You can fix it yourself be changing location.host to location.hostname in the connectDav function of web.api.js

@uggrock uggrock closed this Oct 31, 2014

uggrock added a commit that referenced this issue Oct 31, 2014

fixing the utf8 issues #131 and #134
fixing issue with using webdav of different port #137
@manust

This comment has been minimized.

Show comment
Hide comment
@manust

manust Oct 31, 2014

I confirm, it works now, thanks !

manust commented Oct 31, 2014

I confirm, it works now, thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment