SeaFile Certificate for https but get connection refused

that means it is good?
Dont know what to do. dont get it. dont know hwy there is no such thing...

1 Like

could there be a problem with the ccnet.conf?

1 Like

Do you have a firewall?
if so, it is allowing port 80 in and does it NAT to your internal server?
If not, do you have a modem or cablemodem?
If so, is is set to port forward port 80 to your FritzBox?
If so, does the FritzBox act like a firewall?
If so, then reread this post.
If not, then I don't know why this is failing.

[&2* readers: Get involved; Be heard. It starts with: if you read something you like, then like it :heart:]

1 Like

could there be the problem?

1 Like

Do you mean on the PC or the Router? There is always a Firewall on a FritzBox yes.
Dont know what is NAT.
i got only a fritzbox: https://avm.de/produkte/fritzbox/fritzbox-6490-cable/
So there is no modem. Yes there is a firewall, but i thought i can get ports to be forwarded

1 Like

@GonserJu

Rudy (@rg305) and I are often like the two heads of a giant debating with itself, so please feel free to laugh at our banter. I'm traveling through the foothills of the Rocky Mountains, so my signal is very erratic.

I don't know your network.
I mean: Anything between the Internet and your nginx server.
All pieces must be checked and working as instructed.

[&2* readers: Get involved; Be heard. It starts with: if you read something you like, then like it :heart:]

1 Like

There is only the Fritzbox as Router between it, i think.

2 Likes

Very nice Griffin! Must be very nice!

2 Likes

If the Internet plugs directly to the FritzBox and the server plugs into that (or a switch to that).
Then there are only two things to check:

  • the FritxBox
  • the server

I don't know much about Fritz Boxes, I'll leave that verification to you.
As for the server, it might also have a local firewall installed/running.
And it must be reachable on port 80.
Try from any other device on that network:
http://server.internal.IP.address/

[&2* readers: Get involved; Be heard. It starts with: if you read something you like, then like it :heart:]

1 Like

okay from my network i can reach that SeaFile...
but not from outside!
So there must be something that blocking.

1 Like

You have your mission!

Does the FritzBox have any loggin?
If so, do you see connections to it on port 80?
If no port log entries, then your ISP may be blocking port 80 :frowning:

[&2* readers: Get involved; Be heard. It starts with: if you read something you like, then like it :heart:]

1 Like

Could be something that could make it blocked? There is something that said it will be over a DS-Lite-Tunnel?

1 Like

I really don't know.
Ask you ISP if they allow, or block, TCP port 80 (HTTP).
And check the FritzBox for incoming connection logs.

[&2* readers: Get involved; Be heard. It starts with: if you read something you like, then like it :heart:]

1 Like

no there is no log. only that i provided it to be free.

1 Like

It is. :slightly_smiling_face:

Except the car sickness at points.

1 Like

I dont get it really!

1 Like

How do you eat an elephant?

One bite at a time.

Start with trying to use curl or something like that on your server and see if it responds then move outwards one device at a time until you find the blockage. It will take a bit of effort, but you will find the issue for sure.

1 Like

So griffin and rg,

the problem was the DS-Lite Tunnel. With this sh** from my ISP i could only reach from local on the internet over IPv4, but i got no static IPv4 for my Router and because of the DS Tunnel, i couldnt reach my cloud from outside! So i called my ISP and they tell me they change it! And 5 Minutes later i got my own IPv4 and my Cloud worked. Just when you want to know what was the solution! But thank you very much for your help!

Best regards.

1 Like

Glad you got it working, Julian!

:partying_face:

If you have any other questions or run into any further trouble, just let us know.

1 Like