Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Need to redirect to a different server? |
|
| Author |
|
mark9117
Joined: 01 Nov 2015
Posts: 2
Location: USA
|
 Posted: Sun 01 Nov '15 12:23 Post subject: Need to redirect to a different server? |
 |
|
Greetings all. I am new here and not as good at this stuff as I would like to be, so please be gentle.
I have a specific issue I have no idea how to troubleshoot. I am running a file server that provides a dokuwiki and OwnCloud instances that I can access from where ever. I recently took the plunge and shelled out for a domain name. Prior to that, I was using Dyndns's secondary domain. I don't have a static IP and I'm using Dyndns and ddclient to keep things online.
At any rate, I have implemented SSL and the two basic services that I mentioned above are just fine. However, I also have a MythTV home theater pc serving up MythWeb. Prior to the domain name and SSL success, I just forwarded port 8000 and accessed Mythweb by pointing a browser to http://<my_secondary_domain_at dyndns:8000/mythweb.
Now, I'm pointing the browser to https://<my_domain>:8000/mythweb and getting a "secure connection failed" error. I'm assuming that the SSL connection is failing because I don't have SSL configured on the htpc.
Before I start beating my head against that attempted resolution, can anybody tell me if I'm missing something here? Is there something else I need to consider before spending a lot of time implementing SSL, possibly a small and simple fix that I can use?
What do you say? Can you help a noob out?
Thanks.
Mark
EDIT: This is no surprise, but I thought I'd include it as well.
| Code: | openssl s_client -connect adams-lan.org:8000
CONNECTED(00000003)
140052859569808:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:794:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 316 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
--- |
According to information I have found, this is caused by lack of a certificate on that port. I'm looking into setting up ssl on that server. If anybody has any wisdom, I'd still like to hear it. |
|
| Back to top |
|
mark9117
Joined: 01 Nov 2015
Posts: 2
Location: USA
|
|
| Back to top |
|
|
|
|
|
|
