Socket IO combined with apache ssl server


I'm trying to run a NodeJS server on port 8000 along with my Apache
server which has a ssl certificate. I'm using virtual hosts and
proxypass to link from my apache website through the /node path to my
NodeJS server.



The problem I'm having right is that I'm able to load the pages
served with the Express plugin but the polling from SocketIO
connections seem to fail. I've tried a bunch of things but I just cant
seem to get it to work.



If I setup my client to listen to



var socket = io.connect('example.com:8000', {secure:
false});


My console show something along the lines of this:



socket.io-1.3.7.js:2 GET
https://example.com:8000/socket.io/?EIO=3&transport=polling&t=1451044647116-0
net::ERR_CONNECTION_CLOSED


Also, I know how to use SSL with my NodeJS server but I assume
isn't going to work since I'm also listening through port 443 with my
apache server.



Anyone knows if this is even possible and/or how to set this
up?



EDIT: Forgot to mention I'm running on Ubuntu 14.04 x64

Hi!
I installed apache on Ubuntu server 8.04.1.
I am not
able to run SSL. I checked the intall doc on this site and followed
the install procedure.
I am able to get the "It works!"
page both using http://ip/ and http://ip:443/ but not https://ip/ ( I
get an 'ssl_error_rx_record_too_long' error).
80 and 443 ports
are open
Looking at error log I see this each time I try
https:
Invalid method in request x16x03x01
Anyone has an
idea on how to fix this ?
Ubuntu

I am in the process of migrating a webapp from one server to
another, and the IP address of the servers are different. I need to
change the A record for the domain to the new server. To make sure the
traffic to the old server lands up in the new server I need to setup
reverse proxy in the old server which will redirect all traffic to new
server.



I have several domains in the same server with different SSL
certificates. The client will have a SSL connection the old apache
server and the new server will accept connections through SSL only. So
I need to setup reverse proxy with SSL connection. Is this possible in
apache ? How do I achieve this? I am also worried about slowness due
to two SSL connection setup times.

Web Development

I implemented google's reCAPTCHA V2 on non-https apache shared
server and it worked 100%. I then changed the protocol to my shared
server with SSL using the same script as the non-SSL script. The older
version of reCaptcha had an SSL 'false' to 'true' SSL parameter,
whereas I can't find one for V2.



I had to use htaccess to redirect the example.com to the shared SSL
server https://serverid.net/example/ which works
perfectly without recCAPTCHA. I incorporated reCAPTCHA V2 and the
error message where the reCAPTCHA image should be shows ERROR:
Invalid domain for site key
.



Here's the htaccess:



RewriteEngine On
RewriteCond %{HTTP_HOST} ^(.*)example.com [NC]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://servername.net/example/$1 [R,L]`


href="https://github.com/google/ReCAPTCHA/blob/master/php/recaptchalib.php"
rel="nofollow">Here's the recaptchalib.php code on github in case
that helps:



Anyone know how to make this work?

Network & Servers

I'm trying to connect to Socket IO from an android App with help of
Gottox SocketIO.
it works fine on android versions lower an 4.4 but always gets me a
NullPointerException on V4.4.2!



Connection is established as follows:



    SSLContext ssl_context = null;
try {
ssl_context = SSLContext.getInstance("TLS", "HarmonyJSSE");
} catch (NoSuchAlgorithmException | KeyManagementException |
NoSuchProviderException e) { //
Log.e(LOGIDENT,e.getMessage());
}
_socket = new SocketIO("SOCKETURI");
_socket.connect(new IOCallback() { ... });


Here's the StackTrace:



12-12 15:41:13.355  21152-21308/com.mynamespace
W/System.err﹕ java.lang.NullPointerException
12-12 15:41:13.375 21152-21308/com.mynamespace W/System.err﹕ at
com.android.org.conscrypt.SSLSocketWrapper.initTransportLayer(SSLSocketWrapper.java:48)
12-12 15:41:13.380 21152-21308/com.mynamespace W/System.err﹕ at
com.android.org.conscrypt.SSLSocketImpl.init(SSLSocketImpl.java:186)
12-12 15:41:13.380 21152-21308/com.mynamespace W/System.err﹕ at
com.android.org.conscrypt.SSLSocketImpl.<init>(SSLSocketImpl.java:111)
12-12 15:41:13.385 21152-21308/com.mynamespace W/System.err﹕ at
com.android.org.conscrypt.SSLSocketWrapper.<init>(SSLSocketWrapper.java:37)
12-12 15:41:13.390 21152-21308/com.mynamespace W/System.err﹕ at
com.android.org.conscrypt.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:91)
12-12 15:41:13.400 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.Connection.upgradeToTls(Connection.java:999)
12-12 15:41:13.405 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.Connection.connect(Connection.java:955)
12-12 15:41:13.415 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:411)
12-12 15:41:13.430 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpEngine.sendSocketRequest(HttpEngine.java:343)
12-12 15:41:13.440 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:289)
12-12 15:41:13.440 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:345)
12-12 15:41:13.440 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:296)
12-12 15:41:13.445 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:179)
12-12 15:41:13.450 21152-21308/com.mynamespace W/System.err﹕ at
com.android.okhttp.internal.http.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:246)
12-12 15:41:13.455 21152-21308/com.mynamespace W/System.err﹕ at
io.socket.IOConnection.handshake(IOConnection.java:317)
12-12 15:41:13.460 21152-21308/com.mynamespace W/System.err﹕ at
io.socket.IOConnection.access$600(IOConnection.java:43)
12-12 15:41:13.460 21152-21308/com.mynamespace W/System.err﹕ at
io.socket.IOConnection$ConnectThread.run(IOConnection.java:203)


Does any one know of this problem or a similar one? Or is it
somehow possible to step into
com.android.okhttp.Connection.upgradeToTls as I can't find a row 999
in any of the sources that are available online.

Web Development

Our CXF call with JDK 7 against www1.ecall.ch started
failing after the provider disabled SSLv3 and I don't understand why.
The issue is resolved by setting -Dhttps.protocols=TLSv1
but I'm surprised this is even necessary.



JDK 7/8 support all of SSLv2Hello(2), SSLv3, TLSv1, TLSv1.1 and
TLSv1.2 and I'd expect




  1. the JVM to try top-down during handshake i.e. starting with
    TLSv1.2 first and

  2. to be able to establish a connection even if the server does not
    support SSLv3



Here's the relevant part of the SSL debug log prior to setting
-Dhttps.protocols=TLSv1 i.e. using the JVM defaults (I
cut off the listing of all certs at the beginning):



trigger seeding of SecureRandom
done seeding SecureRandom
trigger seeding of SecureRandom
done seeding SecureRandom
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite:
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_anon_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite:
TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite:
TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite:
TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unsupported cipher suite:
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
Ignoring unsupported cipher suite:
TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
main, setSoTimeout(180000) called
Ignoring unsupported cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 for SSLv2Hello
Ignoring unsupported cipher suite:
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 for SSLv2Hello
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256 for
SSLv2Hello
Ignoring unsupported cipher suite:
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 for SSLv2Hello
Ignoring unsupported cipher suite:
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 for SSLv2Hello
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
for SSLv2Hello
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
for SSLv2Hello
Ignoring unsupported cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 for SSLv3
Ignoring unsupported cipher suite:
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 for SSLv3
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256 for
SSLv3
Ignoring unsupported cipher suite:
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 for SSLv3
Ignoring unsupported cipher suite:
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 for SSLv3
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
for SSLv3
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
for SSLv3
Ignoring unsupported cipher suite:
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite:
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
%% No cached client session
*** ClientHello, SSLv3
RandomCookie: GMT: 1403944475 bytes = { 12, 68, 193, 229, 85, 79, 86,
211, 209, 34, 251, 218, 184, 7, 51, 93, 180, 144, 114, 70, 105, 252,
31, 61, 151, 188, 165, 177 }
Session ID: {}
Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA,
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA,
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA,
TLS_ECDHE_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_SHA,
TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA,
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5,
TLS_EMPTY_RENEGOTIATION_INFO_SCSV, SSL_RSA_WITH_DES_CBC_SHA,
SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA,
SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA,
SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA,
SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_KRB5_WITH_RC4_128_SHA,
TLS_KRB5_WITH_RC4_128_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA,
TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_DES_CBC_SHA,
TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_RC4_40_SHA,
TLS_KRB5_EXPORT_WITH_RC4_40_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA,
TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5]
Compression Methods: { 0 }
Extension elliptic_curves, curve names: {secp256r1, sect163k1,
sect163r2, secp192r1, secp224r1, sect233k1, sect233r1, sect283k1,
sect283r1, secp384r1, sect409k1, sect409r1, secp521r1, sect571k1,
sect571r1, secp160k1, secp160r1, secp160r2, sect163r1, secp192k1,
sect193r1, sect193r2, secp224k1, sect239k1, secp256k1}
Extension ec_point_formats, formats: [uncompressed]
Extension server_name, server_name: [host_name: www1.ecall.ch]
***
[write] MD5 and SHA1 hashes: len = 205
0000: 01 00 00 C9 03 00 54 AE 7E 1B 0C 44 C1 E5 55 4F
......T....D..UO
0010: 56 D3 D1 22 FB DA B8 07 33 5D B4 90 72 46 69 FC
V.."....3]..rFi.
0020: 1F 3D 97 BC A5 B1 00 00 4C C0 09 C0 13 00 2F C0
.=......L...../.
0030: 04 C0 0E 00 33 00 32 C0 07 C0 11 00 05 C0 02 C0
....3.2.........
0040: 0C C0 08 C0 12 00 0A C0 03 C0 0D 00 16 00 13 00
................
0050: 04 00 FF 00 09 00 15 00 12 00 03 00 08 00 14 00
................
0060: 11 00 20 00 24 00 1F 00 23 00 1E 00 22 00 28 00 ..
.$...#...".(.
0070: 2B 00 26 00 29 01 00 00 54 00 0A 00 34 00 32 00
+.&.)...T...4.2.
0080: 17 00 01 00 03 00 13 00 15 00 06 00 07 00 09 00
................
0090: 0A 00 18 00 0B 00 0C 00 19 00 0D 00 0E 00 0F 00
................
00A0: 10 00 11 00 02 00 12 00 04 00 05 00 14 00 08 00
................
00B0: 16 00 0B 00 02 01 00 00 00 00 12 00 10 00 00 0D
................
00C0: 77 77 77 31 2E 65 63 61 6C 6C 2E 63 68 www1.ecall.ch
main, WRITE: SSLv3 Handshake, length = 205
[write] MD5 and SHA1 hashes: len = 179
0000: 01 03 00 00 8A 00 00 00 20 00 C0 09 06 00 40 00 ........
.....@.
0010: C0 13 00 00 2F 00 C0 04 01 00 80 00 C0 0E 00 00
..../...........
0020: 33 00 00 32 00 C0 07 05 00 80 00 C0 11 00 00 05
3..2............
0030: 00 C0 02 00 C0 0C 00 C0 08 00 C0 12 00 00 0A 07
................
0040: 00 C0 00 C0 03 02 00 80 00 C0 0D 00 00 16 00 00
................
0050: 13 00 00 04 01 00 80 00 00 FF 00 00 09 06 00 40
...............@
0060: 00 00 15 00 00 12 00 00 03 02 00 80 00 00 08 00
................
0070: 00 14 00 00 11 00 00 20 00 00 24 00 00 1F 00 00 .......
..$.....
0080: 23 00 00 1E 00 00 22 00 00 28 00 00 2B 00 00 26
#....."..(..+..&
0090: 00 00 29 54 AE 7E 1B 0C 44 C1 E5 55 4F 56 D3 D1
..)T....D..UOV..
00A0: 22 FB DA B8 07 33 5D B4 90 72 46 69 FC 1F 3D 97
"....3]..rFi..=.
00B0: BC A5 B1 ...
main, WRITE: SSLv2 client hello message, length = 179
[Raw write]: length = 181
0000: 80 B3 01 03 00 00 8A 00 00 00 20 00 C0 09 06 00 ..........
.....
0010: 40 00 C0 13 00 00 2F 00 C0 04 01 00 80 00 C0 0E
@...../.........
0020: 00 00 33 00 00 32 00 C0 07 05 00 80 00 C0 11 00
..3..2..........
0030: 00 05 00 C0 02 00 C0 0C 00 C0 08 00 C0 12 00 00
................
0040: 0A 07 00 C0 00 C0 03 02 00 80 00 C0 0D 00 00 16
................
0050: 00 00 13 00 00 04 01 00 80 00 00 FF 00 00 09 06
................
0060: 00 40 00 00 15 00 00 12 00 00 03 02 00 80 00 00
.@..............
0070: 08 00 00 14 00 00 11 00 00 20 00 00 24 00 00 1F .........
..$...
0080: 00 00 23 00 00 1E 00 00 22 00 00 28 00 00 2B 00
..#....."..(..+.
0090: 00 26 00 00 29 54 AE 7E 1B 0C 44 C1 E5 55 4F 56
.&..)T....D..UOV
00A0: D3 D1 22 FB DA B8 07 33 5D B4 90 72 46 69 FC 1F
.."....3]..rFi..
00B0: 3D 97 BC A5 B1 =....
main, handling exception: java.net.SocketException: Connection reset
main, SEND TLSv1 ALERT: fatal, description = unexpected_message
main, WRITE: TLSv1 Alert, length = 2
main, Exception sending alert: java.net.SocketException: Broken pipe
main, called closeSocket()
main, called close()
main, called closeInternal(true)
[...upper part of stacktrace...]
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:196)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
at sun.security.ssl.InputRecord.read(InputRecord.java:480)
at
sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1323)
[...remaining part of stacktrace...]


If I got that right the JVM first tries a SSLv3
Handshake
then a SSLv2 client hello message before
resorting to TLSv1.



But why does it fail after it tries TLSv1 yet when I enable TLS as
the only supported protocol it works? Does the server (IIS 8.5)
attempt some unconventional handshake on which the socket connection
trips over?

Web Development

I'm trying to run a NodeJS server on port 8000 along with my Apache
server which has a ssl certificate. I'm using virtual hosts and
proxypass to link from my apache website through the /node path to my
NodeJS server.



The problem I'm having right is that I'm able to load the pages
served with the Express plugin but the polling from SocketIO
connections seem to fail. I've tried a bunch of things but I just cant
seem to get it to work.



If I setup my client to listen to



var socket = io.connect('example.com:8000', {secure:
false});


My console show something along the lines of this:



socket.io-1.3.7.js:2 GET
https://example.com:8000/socket.io/?EIO=3&transport=polling&t=1451044647116-0
net::ERR_CONNECTION_CLOSED


Also, I know how to use SSL with my NodeJS server but I assume
isn't going to work since I'm also listening through port 443 with my
apache server.



Anyone knows if this is even possible and/or how to set this
up?



EDIT: Forgot to mention I'm running on Ubuntu 14.04 x64

Network & Servers

- Technology - Languages
+ Webmasters
+ Development
+ Development Tools
+ Internet
+ Mobile Programming
+ Linux
+ Unix
+ Apple
+ Ubuntu
+ Mobile & Tablets
+ Databases
+ Android
+ Network & Servers
+ Operating Systems
+ Coding
+ Design Software
+ Web Development
+ Game Development
+ Access
+ Excel
+ Web Design
+ Web Hosting
+ Web Site Reviews
+ Domain Name
+ Information Security
+ Software
+ Computers
+ Electronics
+ Hardware
+ Windows
+ PHP
+ ASP/ASP.Net
+ C/C++/C#
+ VB/VB.Net
+ JAVA
+ Javascript
+ Programming
Privacy Policy - Copyrights Notice - Feedback - Report Violation 2018 © BigHow