File Sharing: cannot connect a folder on Mac / PC

[Salomon]

Hi,

I have a problem with Plesk File Sharing. I am not able to connect it with my Mac
or Windows PC.
I followed the instructions as described in the documentation.

I tried to connect to "https://<my_servername>.net:443/files/shared/" but then a prompt
pops up (mac):

"There was a problem connecting to the server “<my_servername>.net”.
This file server will not allow any additional users to log on. Try to connect
again later."


Then I tried to replace "<my_servername>.net" (which is not a registered domain) with
the IP of the server. Now I can enter my Name and Password (on Mac) but when I
press Connect an error pops up immediately:

"There was a problem connecting to the server “XXX.XX.XXX.XXX”.
Check the server name or IP address, and then try again. If you continue to have
problems, contact your system administrator."
(I don't want to share my IP here... the X's representing numbers)

Also on windows it doesn't work.

Do I have to change some configuration?
Thanks in advance.


PS: I reported my Plesk configuration. The Report ID is TR-PLSK-889.

 

[IgorG]

What sort of output command

telnet IP_of_Plesk_server 443

from your Mac or Windows workstation?

 

[Salomon]

"(...) Connection refused
telnet: Unable to connect to remote host"

 

[IgorG]

Looks like that connection to port 443 on this server is firewalled. Check it.

 

[Salomon]

Hmmm... I don't have a Firewall except for the Plesk firewall.
there I added a rule: Allow incoming from all on ports 443/tcp, 443/udp
I'm not sure if TCP or UDP and also not sure if "incoming" is correct... however, the problem remains the same.

 

[IgorG]

Try to completely disable Plesk firewall and check the connection. You will know that is this Plesk or not issue at least.

 

[Salomon]

I disabled the firewall: problem remains

 

[IgorG]

I disabled the firewall: problem remains

So, it is your network related issue. Check it with your system administrator.

 

[Salomon]

We are a young startup with no dedicated sys admin...

But you mean that the port is blocked by the router in our office?

 

[IgorG]

But you mean that the port is blocked by the router in our office?

Why not as one of possible reason.

 

[Salomon]

I wish I could tell you that it would have been solving it... But unforrtunately this also doesn't seem to be the problem

 

[Salomon]

Hi IgorG,

I still have this problem and I am not sure if our router is forwarding port 443.
We have a Speedlink 5501 which has some issues and is not very flexible (from what I found in the internet).

on this page I checked if the port is open and it tells me that it is closed. So, this means the router doesn't forward the port, right?

Are there certain configurations i have to do on my router?

I have TCP with IPv4, but I also tried different settings...
please help

 

[IgorG]

How can I help you if you can't connect from your workstation to Plesk server - #3 ?
Check on Plesk server that port is up and running with

# lsof -i tcp:443

If it is ok, that it is network connection issue.

 

[Salomon]

Hi IgorG,

thanks for your reply.
I receive the following output when I type in the command:

COMMAND   PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
nginx    1750       root   12u  IPv6 7963094      0t0  TCP therabytes.com:https (LISTEN)
nginx    1750       root   15u  IPv4 7963097      0t0  TCP therabytes.com:https (LISTEN)
nginx    1751      nginx    3u  IPv4 8192896      0t0  TCP therabytes.com:https->pD9F8521C.dip0.t-ipconnect.de:52846 (ESTABLISHED)
nginx    1751      nginx   12u  IPv6 7963094      0t0  TCP therabytes.com:https (LISTEN)
nginx    1751      nginx   15u  IPv4 7963097      0t0  TCP therabytes.com:https (LISTEN)
nginx    1751      nginx   20u  IPv4 8204437      0t0  TCP therabytes.com:https->pD9F8521C.dip0.t-ipconnect.de:50091 (ESTABLISHED)
nginx    1751      nginx   21u  IPv4 8198454      0t0  TCP therabytes.com:https->pD9F8521C.dip0.t-ipconnect.de:60415 (ESTABLISHED)
java     7130       jira  519u  IPv6 6074998      0t0  TCP therabytes.com:38102->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  520u  IPv6 6077662      0t0  TCP therabytes.com:38103->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  524u  IPv6 8204313      0t0  TCP therabytes.com:37264->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  526u  IPv6  591375      0t0  TCP therabytes.com:56171->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  528u  IPv6  577511      0t0  TCP therabytes.com:56173->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  537u  IPv6  599940      0t0  TCP therabytes.com:56354->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  538u  IPv6  599942      0t0  TCP therabytes.com:52935->server-54-230-203-79.fra50.r.cloudfront.net:https (CLOSE_WAIT)
java     7130       jira  587u  IPv6 8167765      0t0  TCP therabytes.com:33886->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  588u  IPv6  604376      0t0  TCP therabytes.com:56330->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  589u  IPv6 8071789      0t0  TCP therabytes.com:52897->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  590u  IPv6  602493      0t0  TCP therabytes.com:56331->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  591u  IPv6 8072447      0t0  TCP therabytes.com:52898->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  592u  IPv6 8073440      0t0  TCP therabytes.com:52900->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  593u  IPv6 8069954      0t0  TCP therabytes.com:52916->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  594u  IPv6 8069953      0t0  TCP therabytes.com:52896->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  595u  IPv6 8071787      0t0  TCP therabytes.com:52893->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  596u  IPv6 8068837      0t0  TCP therabytes.com:52899->pillar03.atlassian.com:https (CLOSE_WAIT)
java     7130       jira  597u  IPv6 8071788      0t0  TCP therabytes.com:52894->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence   66u  IPv6 8198633      0t0  TCP therabytes.com:37052->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  301u  IPv6 8076368      0t0  TCP therabytes.com:53181->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  405u  IPv6 8072745      0t0  TCP therabytes.com:53180->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  445u  IPv6 8204448      0t0  TCP therabytes.com:37351->pillar03.atlassian.com:https (ESTABLISHED)
java    22355 confluence  449u  IPv6 8077330      0t0  TCP therabytes.com:53183->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  450u  IPv6 8014862      0t0  TCP therabytes.com:49943->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  453u  IPv6 8072151      0t0  TCP therabytes.com:53178->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  454u  IPv6 8078358      0t0  TCP therabytes.com:53192->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  550u  IPv6 8072152      0t0  TCP therabytes.com:53179->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  556u  IPv6 8072153      0t0  TCP therabytes.com:53190->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  563u  IPv6 1044376      0t0  TCP therabytes.com:58578->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  567u  IPv6 8075473      0t0  TCP therabytes.com:53191->pillar03.atlassian.com:https (CLOSE_WAIT)
java    22355 confluence  595u  IPv6 1462726      0t0  TCP therabytes.com:53086->pillar03.atlassian.com:https (CLOSE_WAIT)

dunno if that matters, but i changed the main website from "therabytes.com" to "therabytes.net". In the posted log above it still refers to therabytes.com although the file sharing link points to therabytes.net (but I think this is irrelevant because the domain is not registerd and we access everything per IP).

My question before was, if I understood everything correctly.