# PhotoRobot Networking Prerequisites & Configuration The following information contains the detailed networking prerequisites and network configuration for the functional operation of PhotoRobot. ## PhotoRobot Networking Prerequisites & Configuration The following information contains the detailed networking prerequisites and network configuration for the functional operation of PhotoRobot. This technical documentation aims to support existing customers who either do not possess preconfigured equipment, or whose IT department requires independent setup. **Note:** In standard practice, there are preconfigured routers delivered with PhotoRobot to meet networking prerequisites. This helps to both simplify the onboarding of PhotoRobot technology, and to significantly reduce support demands. In this case, the router functions as a small internal network within the customer’s main network. This internal network fully complies with all PhotoRobot communication requirements. Meanwhile, the computer, studio lights (connected via a dedicated Wi-Fi to avoid issues with the customer’s Wi-Fi), all robots, and laser boxes are connected within this isolated subnet. The customer’s studio network then only requires internet access for this small network. Although, when necessary, such as for customers who do not have or are not able to use preconfigured equipment, or who require independent setup, the following network configuration manual is available. This document is under continuous development to support independent network setup. Thus, also refer to any documentation provided to you specifically by PhotoRobot in addition to this online networking configuration manual. **Re-wiring a PhotoRobot router?** If cables were pulled out or moved, see [PhotoRobot Network Equipment and Wiring](https://www.photorobot.com/manuals/photorobot-network-equipment): which port takes your company network (WAN), which ports are for the studio devices (LAN), and diagrams for each router and the Wi-Fi module. ## 1. Networking: PhotoRobot’s Prerequisites This section provides a summary description of the network requirements for PhotoRobot’s functional operation. It includes a protocol / port mapping list, and links to diagnostic tools. Note that each PhotoRobot consists of both a mechanical part and a Control Unit. The Control Unit is either a separate 19” rack-mount unit, or it is built directly into the machine body (such as in Compact machine versions). Further, the Control Unit is connected to the local network. The following Control Unit generations are currently supported: - Control Unit G5 - Control Unit G6 - Control Unit G7 Remote software is available to control PhotoRobot hardware (based on a built-in server). The PhotoRobot Touch application is a remote camera application operated on iOS and iPadOS systems. ### 1.1. PhotoRobot _Controls Software Suite PhotoRobot _Controls Software Suite is the preferred and fully supported software suite that functions with PhotoRobot hardware. The software is in continuous development to support all new versions of PhotoRobot equipment and new versions of supported operating systems on Apple platforms and Windows. ### 1.2. BASIP Software BASIP software was previously provided with PhotoRobot from 2005 - 2015, but is now discontinued. There is now no development or support for BASIP. ### 1.3. SpinMe Studio Software SpinMe Studio Software is supported by SpinMe Ltd. Note: This software package covers **only partial functions** of PhotoRobot hardware. The Control Units also require a **valid PhotoRobot API License** to be managed by this software. ### 1.4 Internet Connection In general, it is necessary to have an internet connection for 100% functionality of PhotoRobot equipment. This is due to the hardware controllers (Control Units Gx), and the software packages. For information on special situations where an internet connection is unavailable or restricted, refer to the Appendix Information at the end of this document. ## 2. PhotoRobot Networking - General Overview The following general overview of PhotoRobot networking is for quick-start information only. It summarizes the modules, Control Unit (G6) parameters, and how to connect PhotoRobot to a customer’s network. For the detailed description of PhotoRobot networking prerequisites, proceed to the next section (3) in this document. ### 2.1. Summary of Modules PhotoRobot is a modular unit. From a networking point of view, there are two modules available: 1. PhotoRobot Equipment 2. Router ### 2.2. Summary of Control Unit (G6) The controller supports a built-in 10/100 ethernet connection, and an RJ45 network interface. Operation in a computer network then requires open ports and protocols as defined in the user manual, [PhotoRobot System Requirements](https://www.photorobot.com/manuals/system-requirements). Additionally, the local PhotoRobot subnet hosting all PhotoRobot components uses the protocols / ports in the following table: | Protocol | Port | Direction | Description | | --- | --- | --- | --- | | TCP | 7777 | outbound | communication with control units version 6 and newer | | TCP | 7778 | outbound | communication with control units version 6 and newer | | UDP | 6666 | outbound | discovering all PhotoRobots (Control Units) on the local network | | UDP | 6660 | inbound | response to UDP broadcast from port 6666 for control units versions 4, 5 | ### 2.3. Connecting PhotoRobot to the Local Network From a networking perspective, PhotoRobot is a network device. PhotoRobot connects to the local network using a standard **ethernet cable**. Wi-Fi connection is not recommended. For diagnostics and troubleshooting, there are the following recommended utilities: - Windows - [frfind.exe for Windows](https://drive.google.com/open?id=0B_V5tu6LfZeXdEFKdzB6WVFWcGc) - Mac OS X - [frfind for macOS](https://drive.google.com/open?id=0B_V5tu6LfZeXTU1CYUZrY1dGdzQ) - Android (discontinued) - [PhotoRobot Locator in Google Play](https://play.google.com/store/apps/details?id=com.photorobot.locator&pcampaignid=web_share) - iPhone, iPad - [PhotoRobot Locator on iTunes](https://itunes.apple.com/au/developer/photorobot-com/id900448053) - Ping - Standard Windows or Mac OS echo request tool within the operating system **Note**: Applications to search for PhotoRobot on the network are also available via links within [PhotoRobot Account Downloads](https://account.photorobot.com/downloads). Additionally, while the Android version of PhotoRobot Locator is now discontinued, this discontinuation is not without replacement – and also concerns the frfind application. To expedite the process, **PhotoRobot _Controls now integrates a tool to locate individual Control Units and open their diagnostic web pages directly in the software**. Ensure you are running the latest version of the software to access this time-saving feature. Then, in order to identify a robot on the network directly within CAPP, open the local version of CAPP, go to Settings, and click **Robots / Control units**. The Robots / Control units menu displays columns with Name, Network, Unit, Version, Discovered, and Identify for each robot. If the dot to the left of the robot name is green, it is online. Clicking the robot field will then open the robot’s website interface. This will also make the LED light on the robot’s Control Unit blink green for its easier identification. ## 3. Detailed PhotoRobot Networking Prerequisites The following information describes in detail the technical configuration of PhotoRobot networking parameters. This section is intended only for use by an experienced system administrator in special cases, and in combination with any supplementary guidance and additional materials provided by PhotoRobots specifically for your installation. **Note:** PhotoRobot is a modular unit consisting of both hardware and software. In terms of networking, PhotoRobot has two modules: the PhotoRobot equipment, and the router connecting PhotoRobot to the local network. ### 3.1. General PhotoRobot Networking Requirements The general networking requirements for PhotoRobot equipment are as follows. - There must be a DHCP server on the local network. It is also not generally recommended to use a fixed IP address for PhotoRobot. If fixed IP addresses are required, refer to [PhotoRobot Support](https://support.photorobot.com/) for guidance. - Local PhotoRobot subnet allows for sending UDP broadcasts to ports 6666, 67, 53. - Accepts UDP broadcasting to address 255.255.255.255, port 6666. - Accepts UDP broadcasting to its broadcast address (for example, 10.1.2.255), port 6666. - An **ethernet cable connection** to the local customer LAN is necessary; one data socket must be available. Avoid Wi-Fi connection. - An internet connection from the local network is necessary for PhotoRobot equipment. In special situations where the local internet connection is unavailable, please contact technical support. - Requirements in the following sections must be met concerning the Control Unit, required protocols and ports for LAN operation, and PhotoRobot Cloud. **No proxy, no SSL/TLS inspection.** Control Units connect directly to the internet and cannot use a proxy server – neither explicit nor transparent, with or without authentication. Outbound HTTPS from the Control Units to as-unirobot.azurewebsites.net (TCP 443) must bypass any web proxy, content filter and SSL/TLS inspection; the server certificate must not be replaced. If the corporate network enforces a proxy for all traffic, exempt the Control Units’ IP or MAC addresses, or connect PhotoRobot through the preconfigured PhotoRobot router with a direct internet uplink. **Symptom of a blocking proxy:** the Control Unit shows “Activation error” and its system log reports “server replied: Forbidden” or “SSL handshake failed”, while the Activation Server receives no request from the unit. See also 7.3. ### 3.2. Control Unit (G4, G5) The Control Unit Generation 4 and Generation 5 are both older versions which are now obsolete and no longer with support or service. In case of failure of the device, upgrading to a newer version is recommended. Versions 4 and 5 are based on RM1 (with dsPIC33F high-performance DSC) or RM32 (with PIC32MX MCU). - The Controller with RM1 supports a built-in 10 Base-T ethernet interface with an RJ45 connector. - The controller with RM2 supports a built-in 10/100 Base-TX ethernet interface with an RJ45 connector. ### 3.3. Required Protocols and Ports for Local Network Operation (G4, G5) For the Control Unit G4 and G5, the following protocols and ports are necessary for operation in a local network. | TCP | 9791 | inbound | The port number can be changed manually, It is used for sending commands or requests from applications into the controller | | TCP | 9791 | outbound | The port number can be changed manually, It is used for acknowledgements or answers from the controller into applications | | TCP | 9792 | outbound | The port number cannot be changed manually and is always higher by 1 than the port described above It is used for sending asynchronous messages from the controller | | TCP | 80 | outbound | http client, calling: activate.khnet.cz | | UDP | 6666 | inbound | UDP server listener for receiving broadcast packets The client application may send this broadcast to discover all PhotoRobots version 4,5,6 connected to the local network | | UDP | 6660 | outbound | Response to UDP broadcast from port 6666 | | UDP | 67 | outbound | asking DHCP server | | UDP | 68 | inbound | DHCP server response | | UDP | 53 | outbound | asking DNS server | | TCP | 53 | outbound | asking DNS server | - *The local network requires UDP broadcasts to be sent to ports 6666, 67, and 53.* - *Local networks must accept UDP broadcasting to address 255.255.255.255, port 6666.* - *Local networks must accept UDP broadcasting to its broadcast address (for example 10.1.2.255), port 6666.* - *It is not required to expose any of the PhotoRobot components directly to the internet via a public IP address nor NAT.* ### 3.4. Control Unit (G6, G7) Control Unit G6 and G7 are based on the Beagle Bone Black platform, which has an ARM Cortex A8 CPU running a customized Xenomai Linux distribution. The controller supports built-in 10/100 ethernet, with an RJ45 network interface for connection to the network. ### 3.5. Required Protocols and Ports for Local Network Operation (G6, G7) The following **protocols and ports are required for operation** of the Control Unit G6 and G7 in a local network. | TCP | 7777 | inbound | PhotoRobot server | | TCP | 7778 | inbound | PhotoRobot server | | TCP | 80 | inbound | http server for controller v6 remote control | | TCP | 80 | outbound | upgrade PhotoRobot | | TCP | 443 | outbound | activation server | | UDP | 6666 | inbound | UDP server listener for receiving broadcast packets Client application may send this broadcast to discover all PhotoRobots versions 4,5,6 connected to the local network | | UDP | 6660 | outbound | Response to UDP broadcast from port 6666 – for compatibility with versions 4, 5. Version 6 responds to the port from which the broadcast was sent. It is a random number with respect to port assignment controlled by client OS. | | UDP | 67 | outbound | asking DHCP server | | UDP | 68 | inbound | DHCP server response | | UDP | 53 | inbound | DNS server, only for wifi connectivity | | UDP | 53 | outbound | asking DNS server | | TCP | 53 | outbound | asking DNS server | - *The local network must allow sending UDP broadcasts to ports 6666, 67, 53.* - *It is not required to expose any of the PhotoRobot components directly to the internet via public IP address nor NAT.* **Note:** Outbound HTTPS from the Control Units to the activation server (TCP 443) must not pass through a proxy server or SSL/TLS inspection. See 3.1. ### 3.6. PhotoRobot Cloud **PhotoRobot Cloud** is an extension of the local PhotoRobot Controls software, and it requires an active license to access the [cloud services on PhotoRobot Cloud](https://cloud2.photorobot.com). All communication is only via the standard secured port **443**. **Note:** Operation in a computer network requires open ports and protocols as defined in [PhotoRobot System Requirements](https://www.photorobot.com/manuals/system-requirements). ## 4. Connecting PhotoRobot to a Customer Network ### 4.1. Connecting PhotoRobot to a Network for the First Time In order to connect PhotoRobot equipment for the first time to a customer’s network, there are the following requirements: 1. PhotoRobot equipment with Control Unit. Check the version; it should be G6, G7, or newer. Control Unit versions G4 and G5 are obsolete and not used for new installations. If you need to install G4 or G5, please contact PhotoRobot Technical Support. 2. Client’s computer. This can be your own PC / Windows or MacOS device. 3. Testing utility for the client’s computer: [**frfind.exe for Windows**](https://drive.google.com/open?id=0B_V5tu6LfZeXdEFKdzB6WVFWcGc), or [**frfind for OS X**](https://drive.google.com/open?id=0B_V5tu6LfZeXTU1CYUZrY1dGdzQ). Download the utility, open the Downloads folder, and double-click “frfind.tar”. This will extract the executable frfind in the Downloads folder. 4. Basic information about the customer’s network. Consult with documentation if available, or with the IT administrators of your company. Regarding the basic information about the customer’s network, attempt to answer the following: 4a. Is there one RJ45 network socket available to connect PhotoRobot? 4b. Is a DHCP server running and distributing IP addresses, DNS info, and GW info? i. If yes, there will be no additional configuration necessary on PhotoRobot or on the client’s computer. ii. If there is no DHCP server, ask for: One static IP address, Network mask, the IP address of a gateway, and the IP address of a DNS server. ### 4.2. Connecting PhotoRobot with the Control Unit G5 If the PhotoRobot Control Unit connected is version G5, use the following instructions to connect PhotoRobot to the customer network. 1. Connect PhotoRobot using a regular ethernet cable to the router; no crossover cable is needed. It is expected that factory settings will be unchanged. This means no static address has been assigned to PhotoRobot, which is working as a DHCP client. No additional network setting is needed if there is a DHCP server in the network. If the static address is required, then configure PhotoRobot based on the steps to connect to a customer’s network for the first time from the previous section of this document (4.b.ii). 2. Switch on the PhotoRobot equipment. 3. Connect the client’s computer to the same router where PhotoRobot is connected. 4. Start testing the frfind utility on the client’s computer as described in the section Basic Connectivity Testing (5.1.). 5. If the frfind testing utility discovers PhotoRobot, the network is ready, and you can begin production using the PhotoRobot Controls application. ### 4.3. Connecting PhotoRobot with the Control Unit G6 If the PhotoRobot Control Unit connecting to the customer’s network is version G6, follow steps 1 - 4 from the previous section (4.2.). Then, note: 1. If the frfind testing utility starts on the client’s computer and discovers PhotoRobot, attempt connecting it from the client’s computer via web browser. To do this, enter the IP address of the discovered PhotoRobot into the browser’s address field, and press enter. This will open PhotoRobot’s service GUI. 2. If the service GUI is successfully reached, this testing phase is complete, and you can begin using the production application PhotoRobot Controls. ### 4.4. Standard Network Modules PhotoRobot delivers pre-configured network modules (a router and an optional Wi-Fi access point) that create a separate studio subnet for all PhotoRobot devices. The devices, their WAN and LAN ports, the wiring and the default network settings are described on [PhotoRobot Network Equipment and Wiring](https://www.photorobot.com/manuals/photorobot-network-equipment). ## 5. Diagnostics and Troubleshooting For diagnostics and troubleshooting of PhotoRobot networking, note it is expected that PhotoRobot has default settings. This means there should be no changed port numbers, and it is acting as a DHCP client. If this is not the case, reset all changes to factory settings first. A typical connection schema includes an intranet infrastructure represented by a switch or router and a DHCP server that gives out IP addresses to clients like PhotoRobots and clients' computers. By default, the following prerequisites must be met. 1. There is a DHCP server up and running, and distributing IP addresses, DNS info, and GW info to clients. 2. There is a network switch supporting 10/100 Base-TX ports, two of which are available for PhotoRobot and the client’s computer. Additional ports may be required to support network-connected accessories, like the FOMEI lights controller, etc. 3. Structured cabling is needed; do not use Wi-Fi. **Warning:** PhotoRobot G6 and the computer running PhotoRobot Controls **must be connected via LAN** (Ethernet) only. Using Wi-Fi or multiple network adapters simultaneously will cause connectivity issues. **The only exception is Broncolor Siros flash units**, which connect through a dedicated Wi-Fi network managed by the PhotoRobot Router (not the computer’s Wi-Fi). The only exception is support requests for unique testing scenarios. ### 5.1. Basic Connectivity Testing If issues arise, it is recommended that the PhotoRobot Control Unit and the client's computer be connected based on the infographic in the previous section, Diagnostics and Troubleshooting (5.). Use the utility application frfind as necessary to discover all PhotoRobot in the local network. **Also, ensure that the operating system on the client’s computer where the utility will run is not running inside of a virtual machine (VMware, Parallels, etc.).** If the operating system is inside of a virtual machine, the frfind utility may not access the local network outside of the client’s computer. ### 5.2. Windows If the client’s OS is Windows, [download the frfind utility](https://drive.google.com/open?id=0B_V5tu6LfZeXdEFKdzB6WVFWcGc) and save the downloaded file frfind.exe to a new local directory, for example: C:\TEMP. (Do not download the utility to Google Drive, a network drive, etc.). Next, run frfind.exe with administrator privileges (or as a restricted user). The Frfind utility searches the local network via all active local network interfaces for all connected and running PhotoRobots. If some are found, the following data displays: - IP address. - MAC address. - Control unit version. - PhotoRobot’s port number. Then, PhotoRobot’s port accessibility is checked. Note that: - All checked ports should be opened. - If one or more ports are closed, the closed port is highlighted in red. - The reason for a closed port can be any networking issue, or the fact that PhotoRobot is currently in use by another application holding the port. The following image displays an example of the above issue on the frfind interface. - In the above issue, there is a problem accessing PhotoRobot 192.168.2.16. because there is no reachable PhotoRobot port. The reason could be a networking issue, or that someone is currently and actively working with the unit, thus occupying the port. - Additionally, note that the network interface IP address 192.168.222.1 which shows that this computer runs on a virtual machine. This could block some applications, such as PhotoRobot Controls, BASIP, or SpinMe from connecting PhotoRobots. ### 5.3. MacOS To run a basic connectivity test on MacOS, download the utility application [frfind for Mac OS X](https://drive.google.com/open?id=0B_V5tu6LfZeXTU1CYUZrY1dGdzQ). Next, open the Downloads folder in Finder and double-click "frfind.tar" to extract the frfind file into the system Downloads. A command window will appear with the search in the process. The local network is scanned via all active local network interfaces for any running PhotoRobots. If some are discovered, their IP and MAC addresses, version, and ports are displayed: **Note:** - All checked ports must be opened. - If a port is closed, it is highlighted in red. - The reason for a closed port could be networking issues like firewall restrictions, or that someone is actively working with the unit, thus occupying the port. ### 5.4. Android **Warning: The Android application is no longer supported as of 2025. Its functionality is fully replaced by features integrated in PhotoRobot Controls.** Running the basic connectivity test on Android requires downloading the PhotoRobot Utility (previously [Locator on Google Play](https://play.google.com/store/apps/details?id=com.photorobot.frfind&hl=cs)), or via [APK download](https://drive.google.com/open?id=1V6FRHRoOt95MLJMLRcMYCWQ-uORvf8-n). Next, connect your Android device via WiFi to the network where PhotoRobot is running, and start the Locator application. Pressing the **Search** button will then search the network for PhotoRobot. If a PhotoRobot is discovered, the following Locator screens will display: If PhotoRobot Control Unit G6 is discovered, the record is active, and two basic functions are available. The first function allows for clicking the record on the left, which opens a web browser accessing the remote control GUI: The second function helps to quickly and visually identify the Control Unit’s physical location by clicking the circle to the right of the record. The Control Unit will then blink the button with the PhotoRobot logo for two seconds. ### 5.5. iOS To run the basic connectivity test on iOS, download the [PhotoRobot Locator utility on the App Store](https://apps.apple.com/au/developer/photorobot-com/id900448053). Next, follow the same instructions as for the Android basic connectivity test in the previous section (5.4.). **Note:** The Locator app is available for iPhone and iPad. ## 6. Recommendations ### 6.1. Activation PhotoRobot Control Units must be activated for functional operation in a production environment. Note that during the activation process, the activation server must connect to the internet. It is also recommended that the new PhotoRobot be activated before transportation to a customer’s location. This requires locally connecting the PhotoRobot system to your own network with internet access, testing the PhotoRobot, and activating PhotoRobot. **Note:** If an internet connection is unavailable or restricted, refer to the Appendix section (8) further in this document. ## 7. Known Issues ### 7.1. PhotoRobot Not Recognized on Local Network If **PhotoRobot is not recognized on the local network**, there are the following possible causes of the issue, with the following solutions: 1. **The client’s computer is blocking communication.** - Try to switch off the firewall temporarily. - Try to switch off any antivirus software temporarily. - Ensure that the frfind utility is not running from a virtual machine (Parallels, VMware, etc.). 1. **The network is blocking communication.** - Ensure the client’s computer is not running a connection through a VPN. - Check if the client's computer and PhotoRobot are correctly connected to the same network. - Ensure that the DHCP server correctly distributes IP addresses, DNS info, and GW info. - Check if network devices (switch, firewall, router) allow communication on the ports listed in this document specific to your system. 1. **PhotoRobot doesn't respond.** - Reset PhotoRobot settings, especially if no static IP address should be set. - Try to connect the PhotoRobot to another network and check if one is recognized. ### 7.2. BASIP Application Does Not Recognize PhotoRobot **Warning: The BASIP application is no longer supported as of 2015. Its functionality is fully replaced by features integrated in PhotoRobot Controls.** The BASIP application in the Windows environment does not use all local network interfaces for searching for PhotoRobots. When there are more of them, BASIP chooses just one for operation. There are the following **Windows adapters**: 1. Vmware virtual ethernet adapter for VMnet8 2. Ethernet adapter Local Area Connection Additionally, note the following parameters. - PhotoRobot is connected to the same network as the Ethernet adapter Local Area Connection. - The BASIP application searches for PhotoRobots on Vmware virtual ethernet adapter for VMnet8. - BASIP does not recognize any PhotoRobot. - The testing utility frfind recognizes PhotoRobot. - The solution is disabling the VMware virtual ethernet adapter for VMnet8 in Windows via network connection settings. - **Tip:** Run the “ncpa.cpl” command from the command line or via shortcut WinKey+R for the network adapters list and management. ### 7.3. Activation Error Behind a Corporate Proxy If the Control Unit shows **“Activation error”** on a corporate network, the most likely cause is a web proxy or SSL/TLS inspection between the Control Unit and the internet. - **Symptom:** the Control Unit’s system log reports “server replied: Forbidden” or “SSL handshake failed”, while the Activation Server receives no request from the unit. - **Solution:** let outbound HTTPS from the Control Units to as-unirobot.azurewebsites.net (TCP 443) bypass the proxy, content filter and SSL/TLS inspection by exempting the Control Units’ IP or MAC addresses, or connect PhotoRobot through the preconfigured PhotoRobot router with a direct internet uplink. See 3.1. ## 8. Appendix Information ### 8.1. Usage with Limited Internet Connection In special situations where an internet connection is unavailable at the installation location (typically military use), alternative methods of using PhotoRobot systems exist. The same applies in regions where selected Google infrastructures are restricted (typically the People's Republic of China). In principle, the following methods to overcome technical or regulatory restrictions are available upon request under special conditions and contracts. **Note: In these situations, there are several limitations to the system's usage.** Please contact the technical support team or your sales engineer to consult the details and **perform pre-installation tests** in your environment. ### 8.2. Control Units Regarding the Control Units (G6 and higher), note they must be activated by a long-term **offline activation key** (for a given repeating period, ex: 12 months). Meanwhile, the initial and subsequent activations are performed via a unique activation string for remote activations provided by the PhotoRobot Support Team electronically. ### 8.3. PhotoRobot Cloud Software Suite Note that the PhotoRobot Cloud Software Suite is not accessible for usage with limited internet connection. Instead, PhotoRobot _Controls is only available in the **local version**. ### 8.4. PhotoRobot Local Software Application PhotoRobot _Controls App must be activated by a long-term **offline activation key** (for a specified repeating period, ex: 12 months). Meanwhile, the first and subsequent activations are performed via a unique activation string for remote activations provided by the PhotoRobot support team electronically. ### 8.5. PhotoRobot Account The PhotoRobot Account (managed in the cloud via a web interface) is not available when Google Cloud is restricted. The cloud account can be reached from a non-restricted area, or the customer has a dedicated e-mail address to manage the **settings**, **billing**, and other account-related issues. ### 8.6. PhotoRobot Support Portal The PhotoRobot Support Portal (managed in the cloud via a web interface) is not available when Google Cloud is restricted. The cloud account can be reached from a non-restricted area, or the customer has a dedicated e-mail address to manage the **support tickets**.