PIXILAB Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
blocks:server:publish-on-internet [2023-01-06 20:10]
admin created 		blocks:server:publish-on-internet [2025-05-30 10:27] (current)
admin Added some cloudflare link for config
Line 1: Line 1:
 ====== Publishing an in-house Blocks server on the Internet ====== ====== Publishing an in-house Blocks server on the Internet ======
  
-This article describes how you can publish an in-house Blocks server so it becomes accessible also through the Internet. This is particularly useful if you want to make your Blocks server accessible to guests sing their own mobile devices. Assuming your location has decent cellular service, this will let your visitors connect to your Blocks server to use it as an audio guide, or similar, based on a Visitor Spot. Since you're using the cellular internet connection already established on all phones, you won't need to provide a wifi network, thereby reducing the technical requirements on site as well as simplifying the onboarding process. A simple, printed QR code can be used to directly connect visitor's phones to your Blocks server.+This article describes how you can publish an in-house Blocks server so it becomes accessible also through the Internet. This is particularly useful if you want to make your Blocks server accessible to guests using their own mobile devices. Assuming your location has decent cellular service, this will let your visitors connect to your Blocks server to use it as an audio guide, or similar, based on a Visitor Spot. Since you're using the cellular internet connection already established on all phones, you won't need to provide a wifi network, thereby reducing the technical requirements on site as well as simplifying the onboarding process. A simple, printed QR code can be used to directly connect visitor's phones to your Blocks server.
  
 ==== Services Used ==== ==== Services Used ====
Line 10: Line 10:
   * A [[https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/|VPN-like tunnel]], making your in-house Blocks server accessible from the internet.   * A [[https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/|VPN-like tunnel]], making your in-house Blocks server accessible from the internet.
   * Certificate for secure server access (HTTPS).   * Certificate for secure server access (HTTPS).
-  * Caching of many resources, such as images, for improved performance and reducer load on your Blocks server.+  * Caching of many resources, such as images, for improved performance and reduce load on your Blocks server.
  
-These services are all currently provided for free by Cloudflare. +These services are all currently provided for free by Cloudflare. This guide assumes you can use Cloudflare also as your DNS provider. However, when that's not an option, you can use a slightly different method based on a [[https://developers.cloudflare.com/cloudflare-one/faq/cloudflare-tunnels-faq/#how-can-tunnel-be-used-with-partial-dns-cname-setup|partial DNS (CNAME Setup)]].
  
 ==== Prerequisites ==== ==== Prerequisites ====
Line 28: Line 28:
   - Log in to your Cloudflare dashboard.   - Log in to your Cloudflare dashboard.
   - If you're not already using Cloudflare as your DNS provider, you may want to set that up and point your registrar to Cloudflare's [[https://www.cloudflare.com/en-gb/dns/|DNS servers]].   - If you're not already using Cloudflare as your DNS provider, you may want to set that up and point your registrar to Cloudflare's [[https://www.cloudflare.com/en-gb/dns/|DNS servers]].
-  - Select "Zero Trust" in the menu on the left hand side. +  - Select **Zero Trust**. 
-  - Select Access under Cloudflare Zero Trust. +  - Select **Networks** under Cloudflare Zero Trust. 
-  - Select Tunnels. +  - Select **Tunnels**. 
-  - Complete setup if requested to. +  - Select **Create a Tunnel** using the "cloudflared" flavor, completing setup if required. 
-  - Enter a "team name" (will also become your URL). +  - Get your Zone and Account IDs from your Accounts page, required below. 
-  - Select the "Free" bundle. +  - Get the token to be used by the tunnel as described [[https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel-api/|here]].
-  - Select Tunnels again under Access. +
-  - Create a tunnel. Set the server-side URL to http: with localhost:8080 as the domain name and port (this assumes Blocks is using its default configuration, with the server listening at port 8080). +
-  - Name your tunnel.+
   - Select the operating system of your server (select Debian, 64 bit if you're running a Blocks server based on our Linux server image).   - Select the operating system of your server (select Debian, 64 bit if you're running a Blocks server based on our Linux server image).
   - Install and run the Cloudflare Connector as instructed.   - Install and run the Cloudflare Connector as instructed.
Line 42: Line 39:
   - Specify a subdomain (if desired) and domain name for the connector.    - Specify a subdomain (if desired) and domain name for the connector. 
   - Wait for the tunnel to be created and show a "healthy" status.   - Wait for the tunnel to be created and show a "healthy" status.
-  - Open a browser using https://<subdomain>.<domain>/edit to access the editor. +  - Open a browser using <code>https://<subdomain>.<domain>/edit</code> to access the editor. 
-  - Connect spots using https://<subdomain>.<domain>/spot. +  - Connect spots using <code>https://<subdomain>.<domain>/spot </code>.
 Substitute <subdomain>.<domain> above with your subdomain (if any) and domain name. Substitute <subdomain>.<domain> above with your subdomain (if any) and domain name.
  
 You're stongly advised to enforce the use of https on all connections, following instructions found [[https://developers.cloudflare.com/ssl/edge-certificates/additional-options/always-use-https/|here]]. Using HTTPS avoids sending passwords and other potentially sensitive data as clear text. You're stongly advised to enforce the use of https on all connections, following instructions found [[https://developers.cloudflare.com/ssl/edge-certificates/additional-options/always-use-https/|here]]. Using HTTPS avoids sending passwords and other potentially sensitive data as clear text.
  
-:!: IMPORTANT; Make sure you have set a secure password for all users of your Blocks server, so you're not using the default "pixi" password for the admin user.+:!: **IMPORTANT**: Make sure you have set a secure password for all users of your Blocks server, so you're not using the default "pixi" password for the admin user.
  
 ==== Recommended Enhancements ==== ==== Recommended Enhancements ====