anodejs/node-ssltunnel

SSL tunnel for node

Introduction

ANODE is a PaaS (Platform as a Service) for developing and hosting node.js WEB applications on Azure.

ANODE is available as a free open source in github. You can clone all ANODE code and have full control over the platform. The steps below guide you in creating your own ANODE deployment.

Features

In a nutshell, ANODE offers the following features:

• Multitenancy - ANODE hosts multiple versions of multiple applications from git repositories and branches, side-by-side.
• Instantaneous deployment - push into git leads to immediate service update in the cloud. ANODE is integrated with github (and bitbucket), supports and leverages github development process.
• Security - ANODE wraps all security handling and exposes HTTPS endpoint. ANODE applications are HTTP servers, agnostic of security.
• Instantaneous logging - ANODE offers instant viewing and querying logs from applications.
• Management dashboard - all management is performed via ANODE's management dashboard. The dashboard is extendable and can be used for managing applications.
• Scale out - ANODE symmetrically deploys applications on Azure instances. Scaleout is opaque to applications.
• Interoperability - ANODE allows applications to collaborate with each other. ANODE itself is implemented as a number of node.js applications.
• Services - there are multiple services offered by ANODE, e.g. scheduling delayed jobs.
• Testing - ANODE supports test suites development and execution.

Terminology

• ANODE farm - Azure cloud service with one production deployment of ANODE role running on several instances.
• Instance - Azure instance (aka VM). We use "Small" sized instances.
• ANODE cluster - Set of several ANODE farms sharing common storage account.

Prerequisites

You need Git to be installed on your development computer. Follow the these steps if you don't have Git yet.

Setup ANODE farm

• The 1st phase - setup basic functional ANODE farm
• The 2nd phase - secure the farm
• The 3rd phase - start deploying applications
• The 4th phase - setup development environment
• Troubleshooting

Reference

node-ssltunnel's Issues

occasional crash on crypto stream

tls.js:96
throw new Error('CryptoStream is not writable');
^
Error: CryptoStream is not writable
at CleartextStream.write (tls.js:96:11)
at Socket. (C:\Users\dimast.MIDDLEEAST\node_modules\ssltunnel\lib\ssltunnel.js:82:27)
at Socket.emit (events.js:67:17)
at TCP.onread (net.js:347:14)

log with error verbosity on errors

NPN support

OpenSSL 1.0.1+ ships with Next Protocol Negotiation (NPN) support, which is required for SPDY protocol negotiation.

node-spdy supports this already, but it would be great to have this support baked right into node-ssltunnel and then deliver the frames over a regular TCP stream.

set keepalive of in cli

remove the commented code on cleartext server keepalive

connect and end logs should be with same level

"node run_ssltunnel.js ..." encounter error

hi.

node run_ssltunnel.js --role client --proxy_port 54080 --server_port 64443 --server_host my-vps-ip --srv_pub_cert ~/node_modules/ssltunnel/gen-certs/server-public.pem --clt_pub_cert ~/node_modules/ssltunnel/gen-certs/client-public.pem --clt_prv_cert ~/node_modules/ssltunnel/gen-certs/client-private.pem
Running 'client' role. Listening on 54080, encrypting and forwarding to ssltunnel's server on my-vps-ip:64443
ssltunnel's client is listening on port: 54080

Connected to the real BE server
/Users/brite/node_modules/ssltunnel/lib/ssltunnel.js:141
log.info('Error communicating with the server. Error: ' + JSON.stringify(exception));
^

TypeError: Converting circular structure to JSON
--> starting at object with constructor 'Object'
--- property 'issuerCertificate' closes the circle
at JSON.stringify ()
at TLSSocket. (/Users/brite/node_modules/ssltunnel/lib/ssltunnel.js:141:70)
at TLSSocket.emit (events.js:208:15)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:77:11)

how to fix it?

support ANY port (when local port 0 is provided)

Error is not shown and have error level at log

Using client mode with log level. I am able to get it listening on a port and says it will forward request and most likely i have a cert issue but I can't tell because it reports this back:

Error communicating with the server. Error: {}
connection to server was closed

I need more info if possible