Once your order is confirmed and payment is processed, we typically prepare your item for dispatch within 1–3 business days. Shipping times vary depending on your location and chosen shipping method. You will receive a shipping confirmation email including a tracking number once the parcel leaves our warehouse.
We ship to all major regions worldwide. For orders delivered outside Italy or the European Union, local import duties, taxes, or handling charges may apply, which are the customer’s responsibility. These fees are not included in your purchase price or shipping fee, unless explicitly stated otherwise. Please check your local customs regulations before placing an order.
If your order has not yet entered the shipping process (i.e., no “shipped” status or tracking code issued), you may request cancellation or amendments (such as changing the shipping address) by contacting us as soon as possible. Once the order is shipped, we cannot guarantee any changes—returns will then follow our returns policy.
We offer a 30 return period from the date of delivery if the item is unused, in its original packaging, and all accessories and documentation are intact. For warranty issues (defective or malfunctioning items), please contact us specifying the order number, product details and a description or photo of the issue. Our standard hardware warranty covers 1 years from date of purchase.
After we ship your item, you will receive an email with a tracking number and a link to the courier’s tracking page. You can log into your account on our website (if registered) to check the order status at any time. If you experience any issues with tracking, just contact our customer support and we’ll help you locate your shipment.
Yes — we accept international orders outside the EU. For non-EU shipments, no Italian VAT (VAT at 22%) is applied as the transaction is treated as an export. The final cost may include import VAT, customs duties, or other fees in your country, which are your responsibility. For orders within the EU you may be subject to local VAT rules (for example, via OSS) depending on your status (consumer or business).
The download is available here (v7_20260612), use BalenaEtcher or dd to replicate teh filesystem on a MSATA disk or USB drive.
How to remove the mSATA disk and flash it using a USB mSATA adapter
A USB mSATA adapter is very easy to find online and usually costs around €10 on Amazon.
Important: handle the disk carefully, avoid touching the gold contacts, and make sure the board is fully powered off before removing it.
FoxBox units shipped before June 5, 2026 may be affected by a possible network issue where the Ethernet interface receives both:
This can lead to:
Connect to the FoxBox via SSH:
ssh [email protected]
(default user foxbox password foxbox)
then check
ip -br addr show enp3s0
ip route
The network interface enp3s0 should have only one IP address assigned:
192.168.1.98/24
if you see 2 ip addresses example:
enp3s0 UP 192.168.1.98/24 192.168.1.120/24
then the unit is affected by this issue and the DHCP configuration must be disabled.
Run the following commands:
echo ‘network: {config: disabled}’ | sudo tee /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
sudo mv /etc/netplan/50-cloud-init.yaml \
/etc/netplan/50-cloud-init.yaml.disabled
sudo netplan generate
sudo netplan apply
Run the following commands again:
ip -br addr show enp3s0
ip route
and you should have
192.168.1.98/24
with no additional DHCP-assigned addresses.
In most cases, no reboot is necessary. The changes take effect immediately after running:
sudo netplan apply
However, if network connectivity remains inconsistent after applying the fix, a system reboot may be performed as an additional precaution.
In some cases, a FoxBox may power on but fail to complete the normal startup sequence.
Typical symptoms include:
In most cases, this behavior is caused by an incorrect BIOS configuration, often related to storage device settings. Restoring the BIOS to its factory default settings typically resolves the issue.
Before starting, connect:
These devices are required to access the BIOS setup utility.
DELuntil the BIOS Setup Utility appears on the monitor.
Save & Exit
→ Restore DefaultsAlternatively, on some BIOS versions, you can press:
F9to load the default configuration.
Save & Exit
→ Save Changes and Resetor press:
F10and confirm.
After the reboot:
If the startup beep is still missing after restoring BIOS defaults:
The FoxBox BIOS contains configuration parameters that control storage initialization and boot device detection. In rare cases, these settings can become misconfigured, preventing the system from completing the startup sequence.
Restoring the factory defaults returns all BIOS settings to their validated configuration and resolves the vast majority of startup issues related to BIOS misconfiguration.
FoxBox units shipped before May 25, 2026 may be affected by one or more configuration issues related to:
To simplify recovery, a maintenance script named:
foxbox_fix_kannel_autoconfig.shcan be executed directly on the FoxBox. The script automatically applies a series of corrective actions that resolve the most common issues found on older deployments.
Connect to the FoxBox via SSH:
ssh [email protected]Password:
foxboxCopy the script to the FoxBox using SCP, SFTP, WinSCP, FileZilla, or any preferred file transfer tool.
For example:
scp foxbox_fix_kannel_autoconfig.sh [email protected]:/home/foxbox/cd /home/foxboxchmod +x foxbox_fix_kannel_autoconfig.sh./foxbox_fix_kannel_autoconfig.shThe script will automatically create backups before modifying any configuration files.
The script replaces the modem auto-detection logic with a more robust implementation that:
smsc definitions;This resolves issues where modems are detected inconsistently after reboot or reconnection.
The script recreates the default incoming SMS service configuration:
group = sms-service
keyword = default
catch-all = yesThis ensures that inbound messages are properly forwarded to the FoxBox application instead of being rejected or generating unexpected automatic responses.
The script rebuilds Kannel routing rules based on detected modems and automatically distributes traffic across all available GSM devices.
This resolves situations where:
The script updates the Kannel proxy behavior to correctly interpret successful HTTP responses even when the remote server returns an empty response body.
This resolves false transmission failures caused by proxy validation logic.
The script automatically disables obsolete webhook capture configurations that may interfere with SMS processing.
This prevents messages from being redirected to outdated debugging endpoints.
The script restores the recommended values for:
This resolves several issues related to gateway communication and delivery report processing.
After applying the fixes, the script automatically:
The script automatically restarts:
bearerbox
smsboxallowing the new configuration to become active immediately.
At the end of execution you should see messages similar to:
[fix] verify
[fix] restart kannel
[fix] smokewithout any fatal errors.
The script also performs an internal connectivity test to verify that the SMS processing chain is functioning correctly.
Yes.
The script:
This maintenance script is recommended primarily for:
FoxBox units shipped before May 25, 2026
where one or more of the above configuration issues may be present.
Systems shipped after this date already include the corrected configuration and generally do not require this procedure.
This procedure is intended as a preventive maintenance action and can safely be executed even if the specific issue has not yet been observed.
DOWNLOAD FIX (zip archive is password protected password is foxbox)
foxbox_fix_kannel_autoconfig
phpMyAdmin Docker Upgrade Procedure (Keeping Proxy
and Network Intact)
This document describes the verified procedure used to upgrade the phpMyAdmin Docker container to a newer
PHP/phpMyAdmin version in order to mitigate CVEs affecting the previous PHP runtime, while keeping the
existing Docker network and NGINX reverse proxy configuration fully operational.
1. Backup Current Configuration
cd ~
sudo docker inspect phpmyadmin > phpmyadmin.backup.inspect.json
sudo docker logs phpmyadmin > phpmyadmin.backup.logs.txt 2>&1
2. Check Existing Environment Variables
sudo docker inspect phpmyadmin –format ‘{{range .Config.Env}}{{println .}}{{end}}’
3. Pull Updated phpMyAdmin Image
sudo docker pull phpmyadmin:5.2.3
4. Stop and Backup Existing Container
sudo docker stop phpmyadmin
sudo docker rename phpmyadmin phpmyadmin_old
5. Recreate the Container on the Existing Docker Network
sudo docker run -d \
–name phpmyadmin \
–network foxnet \
-p 8081:80 \
-e PMA_HOST=mysql8 \
-e PMA_PORT=3306 \
-e PMA_ABSOLUTE_URI=https://YOUR_DOMAIN/phpmyadmin/ \
–restart unless-stopped \
phpmyadmin:5.2.3
6. Verify Container Status
sudo docker ps
sudo docker logs –tail=100 phpmyadmin
curl -I http://localhost:8081
7. Reload NGINX Configuration
sudo docker exec nginx_proxy nginx -t
sudo docker exec nginx_proxy nginx -s reload
8. Test Access
https://YOUR_DOMAIN/phpmyadmin/9. Remove Old Container After Successful Verification
sudo docker rm phpmyadmin_old
10. Rollback Procedure (if needed)
sudo docker stop phpmyadmin
sudo docker rm phpmyadmin
sudo docker rename phpmyadmin_old phpmyadmin
sudo docker start phpmyadmin
Important Notes
– The existing NGINX reverse proxy configuration remains valid because the container name phpmyadmin and
Docker network foxnet were preserved.
– The updated container is now running:
– phpMyAdmin 5.2.3
– PHP 8.3.26
– This upgrade is expected to resolve CVEs related to older PHP versions previously bundled inside the container image previously to 31/05/2026
The FoxBox responds to network pings, but the web interface is not accessible and the browser displays a 502 Bad Gateway error.
Connect an HDMI monitor and a USB keyboard directly to the FoxBox.
When the login prompt appears, use the following credentials:
Username: foxbox
Password: foxbox
Check that the network interface ens3 has the expected IP address:
ip addr show ens3Verify that the interface has an address similar to:
192.168.1.98If the IP address is missing or incorrect, verify the network configuration before proceeding.
If the IP address is correct but the web interface is still unavailable, execute the following commands:
sudo docker update --restart unless-stopped nginx_proxy
sudo docker update --restart unless-stopped goffy_pare_modThen restart the containers:
sudo docker restart nginx_proxy
sudo docker restart goffy_pare_modWait approximately 30 seconds and refresh the browser.
The FoxBox web interface should now be accessible.
A 502 Bad Gateway error usually indicates that the NGINX reverse proxy (nginx_proxy) is unable to communicate with the backend application (goffy_pare_mod). Restarting the containers and ensuring that Docker restart policies are correctly configured typically resolves the issue.
ens3 has a valid IP address (e.g. 192.168.1.98).
A compact and reliable on-premise SMS gateway designed for small to mid-scale deployments. FoxBox S1 gives you full control over SMS delivery, integrations and data, making it ideal for alerts, transactional messaging and secure internal communications.
FoxBox S2 extends the S1 capabilities with dual modem support for redundancy and load balancing. Built for mission-critical use cases, it ensures higher availability and resilience while keeping all SMS traffic inside your infrastructure.
FoxBox RS is a rack-mount SMS gateway designed for enterprise and large-scale environments. With multi-SIM support, high throughput and advanced integration options, it enables centralized, compliant and scalable SMS communication across complex infrastructures.
How to remove the mSATA disk and flash it using a USB mSATA adapter
A USB mSATA adapter is very easy to find online and usually costs around €10 on Amazon
Important: handle the disk carefully, avoid touching the gold contacts, and make sure the board is fully powered off before removing it.
