Used to remotely manage services including DHCP server or DNS server.
Used when failing over with a virtual hostname to update the virtual hostname's DNS entry and for periodic monitoring. Open the port to enable communication from all polling engines (both Main or Additional) to the Additional Web Server, and from the Additional Web Server to polling engines. The port used for SSL-encrypted RabbitMQ messaging from the Additional Web Server to the Main Polling Engine. Open the port from your Orion Web Console to the SQL Server. The port used for communication between the SolarWinds server and the SQL Server. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the web console is. If you specify any port other than 80, you must include that port in the URL used to access the web console. Open the port to enable communication from your computers to the Orion Web Console. The port used for communication between the Additional Polling Engine and the Main Polling Engine.ĭefault additional web server port. The port used for SSL-encrypted RabbitMQ messaging from the Main Polling Engine to the Additional Polling Engine. Required only if your SQL Server is configured to use dynamic ports.
The port used for communication with the SQL Server Browser Service (Orion database) and the APE to determine how to communicate with certain non-standard SQL Server installations. The port used for communication between the APE and the Orion database. The port used by the APE for receiving trap messages from devices. The port used by the additional polling engine (APE) to query for SNMP information on the device and to send it to the APE. The following ports are the minimum required for an Additional Polling Engine to ensure the most basic functions. In case of a long list, a max of 10 links will show (if -1, that means all links will show) Orion Platform products Ports for Orion Platform featuresĪdditional Polling Engines (APE) have the same port requirements as the Main Polling Engine. Ssl_dhparam /etc/letsencrypt/ssl-dhparams.The Custom TOC will appear here, created based on h1,h2,h3,h4 used in this topic. Ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem Ssl_certificate_key /etc/letsencrypt/live//privkey.pem Ssl_certificate /etc/letsencrypt/live//fullchain.pem Note that we are using which, inside of the nginx container configured using docker-compose, will point to the ipfs container managed by docker-compose. And then we proxy most of the traffic to the ipfs container. On the HTTPS side, we are pointing to our certificate folder and nginx configuration that we will get from certbot. You'll notice that this directory is shared with the certbot docker image. For the HTTP server, we give it a name (in my case ) and redirect everything to the https server, except the location /.will-known/acme-challenege/ which certbot is going to use to negotiate with the letsencrypt servers to generate our certficate. We configure nginx to listen on ports 80 and 443. 8080 is the local gateway which will we expose only to localhost, 8081 is where we are going to run the websocket listener – we will proxy through nginx later in this document, and 5001 is the api server which should not be exposed externally. If you are running a firewall you should unblock that port. 4001 is the ipfs swarm port and needs to be open to the world.
This is to keep any local data around if you remove the server or decide to upgrade your installation, but it's not strictly necessary if you are using this as a sort of cache. We will also define the storage directory in /ipfsdata which we will mount to the local file system in. The IPFS_PROFILE environment variable is used on the initial repository installation configure a specific profile, in this case server, which will remove some of the local network scanning stuff that could make your hosting provider uneasy.
We are going to pull from the official ipfs docker image. I'm using a prebuilt docker image on Digital Ocean but the key part is to get the domain name. Setup certbot to auto renew the certificatesĪ server with a domain or subdomain to use certbot to get a certificate
Lets walk through how to setup a IPFS server that your browser code can connect to in addition to the public gateways. IPFS nodes that run in the broswer communicate over websockets to the main network. Published Septem#howto, #ipfs, #docker, #docker-compose, #certbot Setting up an IPFS Node using docker-compose and certbot