Newbie needs help getting Filecloud with SSL running


oh well. Tomorrow's problem.

Are you running a web service in that server?

2 Likes

I wasn't going to but someone said to open port 80 so I enabled IIS.
The only intention was for "Filecloud" to run on the server so we can have access to our files on our phones and remotely.

Here is my router port forwarding. Is this correct?

Those are two different things.
Some one said:
Open the gate to your driveway
So, I bought a car.

Is there also a second router?
[provided by the ISP]

2 Likes

LOL.... Looks like IIS is working and live so port 80 should be open now.
I tried running "certbot certonly --standalone" and still getting challenge errors.
The comcast router is in bridge mode. I'll recheck though

1 Like

One, you can't use --standalone when something else is using port 80. Standalone requires binding to port 80.

Two, I thought you wanted to use Apache. Why are you using IIS?

Three, if you want to use IIS it would probably be easier to use something like Certify The Web instead of Certbot. It is a gui designed for Windows and integrates with IIS better than Certbot. See:

6 Likes

I guess I'm not sure how to open and close ports. I added iis simply because In my mind uses port 80. Easy enough to change but how do I open port 80 for certbot's use?

Regarding webserver I believe Filecloud uses apache. Thanks for the help with this ultra newbie

You should make sure that's true. And, if so, start by getting Apache running on port 80. You will have to stop IIS.

Then use Certbot certonly --webroot rather than --standalone. This will use the running Apache to get a cert. You then manually configure Apache for HTTPS once you get a cert. See Mozilla configurator for suggestions (link here)

3 Likes

For sure. Verified that "filecloud" in fact uses apache. apache has its own folder within the "filecloud xampp directory.

2 Likes

Okay,
Turns out my server 2016 had both ports 80 and 443 in and out shut down. Looks like Filecloud is working in port 80.
Can you all help kick start the process of using secured port 443?
*I have additionally allowed 443 in and out on the server

Is that running on another server?

2 Likes

Thanks for the reply
I only have 1 server its os is windows 2016
Web server: apache
Both 80 and 443 opened for in and out traffic

1 Like

Do you know how to configure Apache?

3 Likes

I believe configuration its done through httpd.conf
Looks like httpd.conf was set with basic commands during filecloud setup.
I can perform basic edits though.
I believe the # line items are disregarded
So to answer your question....Limited.
But I can tell you, Apache is up and running on port 80. Just not securely encrypted on port 443.

Ok.
Where you able to get a cert?
[if so, what shows?: certbot certificates]

2 Likes

I was able to get a cert but following installation from within filecloud, Since then Apache service won't start.
The error log shows the following.

[Thu Mar 16 20:44:21.306611 2023] [mpm_winnt:notice] [pid 2200:tid 388] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Thu Mar 16 20:44:23.308772 2023] [mpm_winnt:notice] [pid 3704:tid 416] AH00364: Child: All worker threads have exited.
[Thu Mar 16 20:44:24.199859 2023] [mpm_winnt:notice] [pid 2200:tid 388] AH00430: Parent: Child process 3704 exited successfully.
[Thu Mar 16 21:15:13.787257 2023] [ssl:emerg] [pid 8340:tid 384] AH02565: Certificate and private key www.example.com:443:0 from C:/xampp/apache/conf/ssl.crt/server.crt and C:/xampp/apache/conf/ssl.key/server.key do not match
AH00016: Configuration Failed
[Thu Mar 16 21:15:34.078355 2023] [ssl:emerg] [pid 9648:tid 384] AH02565: Certificate and private key www.example.com:443:0 from C:/xampp/apache/conf/ssl.crt/server.crt and C:/xampp/apache/conf/ssl.key/server.key do not match
AH00016: Configuration Failed
[Thu Mar 16 21:17:44.451006 2023] [ssl:emerg] [pid 2432:tid 108] AH02565: Certificate and private key www.example.com:443:0 from C:/xampp/apache/conf/ssl.crt/server.crt and C:/xampp/apache/conf/ssl.key/server.key do not match
AH00016: Configuration Failed
[Thu Mar 16 21:42:59.425232 2023] [ssl:emerg] [pid 5576:tid 364] AH02565: Certificate and private key www.example.com:443:0 from C:/xampp/apache/conf/ssl.crt/server.crt and C:/xampp/apache/conf/ssl.key/server.key do not match
AH00016: Configuration Failed
[Thu Mar 16 21:44:39.425076 2023] [ssl:emerg] [pid 5804:tid 348] AH02565: Certificate and private key www.example.com:443:0 from C:/xampp/apache/conf/ssl.crt/server.crt and C:/xampp/apache/conf/ssl.key/server.key do not match
AH00016: Configuration Failed
[Thu Mar 16 22:06:06.834911 2023] [ssl:emerg] [pid 3112:tid 388] AH02565: Certificate and private key www.example.com:443:0 from C:/xampp/apache/conf/ssl.crt/server.crt and C:/xampp/apache/conf/ssl.key/server.key do not match
AH00016: Configuration Failed

The error explains the problem well. That server.crt and server.key file are not a valid cert and private key. I see you got a Let's Encrypt cert today but how did these files in the /xampp/apache/... folder get created?

4 Likes

Thanks for the reply.

I used the filecloud control panel to install the cert

Well, that panel didn't use your new Let's Encrypt certs. I don't know Filecloud. It does not come up often in this forum but maybe someone else will know.

Or, try the Filecloud community

3 Likes