changed ports

docs/root/source/installation/api/http-samples/api-index-response.http

@@ -7,7 +7,7 @@ Content-Type: application/json
   "docs": "https://docs.bigchaindb.com/projects/server/en/v2.2.2/http-client-server-api.html",
   "metadata": "/metadata/",
   "outputs": "/outputs/",
-  "streams": "ws://localhost:9985/api/v1/streams/valid_transactions",
+  "streams": "ws://localhost:3333/api/v1/streams/valid_transactions",
   "transactions": "/transactions/",
   "validators": "/validators"
 }

docs/root/source/installation/api/http-samples/index-response.http

@@ -9,7 +9,7 @@ Content-Type: application/json
       "docs": "https://docs.bigchaindb.com/projects/server/en/v2.2.2/http-client-server-api.html",
       "metadata": "/api/v1/metadata/",
       "outputs": "/api/v1/outputs/",
-      "streams": "ws://localhost:9985/api/v1/streams/valid_transactions",
+      "streams": "ws://localhost:3333/api/v1/streams/valid_transactions",
       "transactions": "/api/v1/transactions/",
       "validators": "/api/v1/validators"
     }

docs/root/source/installation/api/websocket-event-stream-api.rst

@@ -12,7 +12,7 @@ The WebSocket Event Stream API
 .. important::
     The WebSocket Event Stream runs on a different port than the Web API. The
     default port for the Web API is `3333`, while the one for the Event Stream
-    is `9985`.
+    is `3333`.
 
 BigchainDB provides real-time event streams over the WebSocket protocol with
 the Event Stream API.
@@ -40,7 +40,7 @@ response contains a ``streams`` property:
 
     {
      ...,
-     "streams": "ws://example.com:9985/api/v1/streams/valid_transactions",
+     "streams": "ws://example.com:3333/api/v1/streams/valid_transactions",
      ...
     }
 

docs/root/source/installation/appendices/firewall-notes.md

@@ -15,7 +15,7 @@ The following ports should expect unsolicited inbound traffic:
 
 1. **Port 22** can expect inbound SSH (TCP) traffic from the node administrator (i.e. a small set of IP addresses).
 1. **Port 3333** can expect inbound HTTP (TCP) traffic from BigchainDB clients sending transactions to the BigchainDB HTTP API.
-1. **Port 9985** can expect inbound WebSocket traffic from BigchainDB clients.
+1. **Port 3333** can expect inbound WebSocket traffic from BigchainDB clients.
 1. **Port 26656** can expect inbound Tendermint P2P traffic from other Tendermint peers.
 1. **Port 9986** can expect inbound HTTP (TCP) traffic from clients accessing the Public Key of a Tendermint instance.
 
@@ -53,9 +53,9 @@ If Gunicorn and the reverse proxy are running on the same server, then you'll ha
 
 You may want to have Gunicorn and the reverse proxy running on different servers, so that both can listen on port 3333. That would also help isolate the effects of a denial-of-service attack.
 
-## Port 9985
+## Port 3333
 
-Port 9985 is the default port for the BigchainDB WebSocket Event Stream API.
+Port 3333 is the default port for the BigchainDB WebSocket Event Stream API.
 
 ## Port 9986
 

docs/root/source/installation/network-setup/k8s-deployment-template/node-on-kubernetes.rst

@@ -693,7 +693,7 @@ To test the BigchainDB instance:
 
    $ curl -X GET http://bdb-instance-0:26657/abci_info
 
-   $ wsc -er ws://bdb-instance-0:9985/api/v1/streams/valid_transactions
+   $ wsc -er ws://bdb-instance-0:3333/api/v1/streams/valid_transactions
 
 
 To test the OpenResty instance:

docs/root/source/installation/node-setup/all-in-one-bigchaindb.md

@@ -39,7 +39,7 @@ $ docker run \
   --detach \
   --name bigchaindb \
   --publish 3333:3333 \
-  --publish 9985:9985 \
+  --publish 3333:3333 \
   --publish 27017:27017 \
   --publish 26657:26657 \
   --volume $HOME/bigchaindb_docker/mongodb/data/db:/data/db \
@@ -54,7 +54,7 @@ Let's analyze that command:
 * `--detach` run the container in the background
 * `publish 3333:3333` map the host port `3333` to the container port `3333`
  (the BigchainDB API server) 
-  * `9985` BigchainDB Websocket server
+  * `3333` BigchainDB Websocket server
   * `27017` Default port for MongoDB
   * `26657` Tendermint RPC server
 * `--volume "$HOME/bigchaindb_docker/mongodb:/data"` map the host directory

docs/root/source/installation/node-setup/configuration.md

@@ -171,15 +171,15 @@ which is used to serve the
 (but setting it to `"wss"` does *not* enable SSL/TLS).
 `wsserver.host` is where to bind the aiohttp server socket and
 `wsserver.port` is the corresponding port.
-If you want to allow connections from anyone, on port 9985,
-set `wsserver.host` to 0.0.0.0 and `wsserver.port` to 9985.
+If you want to allow connections from anyone, on port 3333,
+set `wsserver.host` to 0.0.0.0 and `wsserver.port` to 3333.
 
 **Example using environment variables**
 
 ```text
 export BIGCHAINDB_WSSERVER_SCHEME=ws
 export BIGCHAINDB_WSSERVER_HOST=0.0.0.0
-export BIGCHAINDB_WSSERVER_PORT=9985
+export BIGCHAINDB_WSSERVER_PORT=3333
 ```
 
 **Example config file snippet**
@@ -198,7 +198,7 @@ export BIGCHAINDB_WSSERVER_PORT=9985
 "wsserver": {
     "scheme": "ws",
     "host": "localhost",
-    "port": 9985
+    "port": 3333
 }
 ```
 
@@ -233,7 +233,7 @@ export BIGCHAINDB_WSSERVER_ADVERTISED_PORT=443
 "wsserver": {
     "advertised_scheme": "ws",
     "advertised_host": "localhost",
-    "advertised_port": 9985
+    "advertised_port": 3333
 }
 ```