Changelog
2025.11-02
smoxy 2025.11-02 will be available from November 28, 2025. This release introduces major new features including Performance Check, a redesigned rules system, and Under Attack Mode.
⭐ New Feature: Performance Check
smoxy now includes a comprehensive performance testing suite to measure, monitor, and optimize your website's speed.
Run synthetic performance tests on any URL to measure Core Web Vitals (LCP, FCP, CLS, TBT, TTFB), analyze resource loading, and identify bottlenecks. Each test provides a performance score (0-100), detailed resource breakdowns for CSS, JavaScript, images, and fonts, plus third-party impact analysis showing which external services affect your load time.
Create collections of URLs for automated, scheduled testing. Monitor multiple pages over time, track performance trends, and catch regressions before they impact users. Suites can be enabled or disabled without deletion, and if the same URL appears in multiple suites, test results are shared efficiently.
An AI-powered assistant that analyzes your actual test results and provides specific, actionable recommendations. Attach any Performance Check result to get personalized advice based on your real metrics, file URLs, and resource configuration. The Coach prioritizes recommendations by impact (Critical → Quick Win → High Impact → Optimization) and specifically suggests smoxy features where applicable.
The three features work together: run a test, review results, ask the Coach for guidance, implement changes, test again, then set up a suite for ongoing monitoring.
⭐ New Feature: Under Attack Mode
Under Attack Mode provides emergency protection during DDoS attacks or unusual traffic spikes. When enabled, every visitor must pass a non-interactive challenge before accessing your site, filtering out most automated attack traffic while allowing legitimate users through.
Key points:
Activate via Quick Actions in your site Dashboard
Challenge page appears to all visitors during protection
Designed for temporary use during active attacks
Disable immediately once the attack subsides to restore normal user experience
For permanent bot protection without affecting all visitors, use Access Rules instead.
Access Rules let you control access to your site based on request characteristics like IP addresses, geographic location, user agents, headers, and more. They execute first in the rule sequence, before any other processing including WAF.
Actions available:
Allow: Bypass all security measures, including Under Attack Mode and future security features
Block: Deny access completely
Challenge: Require JavaScript verification
Skip: Skip security checks for trusted traffic
Example use cases:
Block traffic from specific countries
Challenge requests from suspicious IP ranges
Whitelist your office IP addresses
Block known bad user agents
Rewrite Rules modify the request URL based on pattern matching, using nginx-style URL rewriting. They execute second in the rule sequence (after Access Rules, before Page and Conditional Rules), ensuring URL transformations happen before other rules evaluate the URL.
Key characteristics:
Transform URLs before cache lookup
nginx-style pattern matching and rewriting
First match wins, then stops
Evaluated in position order
Example use cases:
Redirect legacy URL structures to new paths
Add or remove trailing slashes
Rewrite language prefixes
Map vanity URLs to actual paths
⭐ New Feature: WebSocket Support
smoxy now supports WebSocket (WS/WSS) connections, allowing real-time bidirectional communication between clients and your backend servers. WebSocket upgrades are automatically handled and proxied through smoxy, making it seamless to run real-time applications like:
Live chat and messaging
Real-time notifications
Collaborative editing tools
Live dashboards and monitoring
Page Rules are now deprecated and will be removed in a future version. Please use Conditional Rules for all new rules.
Why switch to Conditional Rules?
No performance difference: Conditional Rules are just as fast
Better overview: All setting changes in one place
Easier debugging: Page Rules used nginx-style location logic where only the "best" match won, making it difficult to understand which rule applied. Conditional Rules evaluate transparently in position order
More flexibility: Conditional Rules offer rich conditions (IP, country, headers, cookies, user agents, and more)
Migration: To migrate a Page Rule, create a Conditional Rule with a URI condition matching your URL pattern. Existing Page Rules continue to work but should be migrated when possible.
2025.11-01
smoxy 2025.10-01 is available as of November 10, 2025.
✅ Bug fix: Added a new validation rule that verifies referenced Basic Auth users actually exist in a site's configuration before allowing page rules to be created or updated
⭐ New Feature: Real User Monitoring (RUM) is now released and available to all users.
Real User Monitoring allows you to track and analyze actual user experiences on your website in real-time, providing valuable insights into performance metrics, user behavior, and potential issues affecting your visitors.
Open Source Dashboard Integration: We're excited to announce our new open source repository at https://github.com/smoxy-eu/rum-dashboard, which provides an example implementation of how to fetch your Real User Monitoring data via API and visualize it in Grafana.
Create Custom Dashboards: While smoxy continues to collect and store your RUM data, you now have complete freedom to use this data however you like. Build highly customizable Grafana dashboards tailored to your specific needs and monitoring requirements.
Full API Access: The open source project demonstrates best practices for accessing your RUM data programmatically, enabling you to integrate monitoring data into your existing observability stack or create entirely custom visualization solutions.
This feature empowers you to maintain full control over how you analyze and present your user monitoring data, combining the reliability of smoxy's data collection with the flexibility of your own dashboards.
2025.10-01
smoxy 2025.10-01 is available as of October 30, 2025.
✅ Bug fix: A bug was fixed which prevented users from removing IPs from IP lists.
✅ Bug fix: An error was fixed when displaying the currently selected organization in the navigation sidebar.
✅ Bug fix: When a conditional rule matcher was set to Equals, users were not able to change that setting again and had to create new conditional rules instead, to change the matcher.
✅ Bug fix: When adding many new domains (100+) in an IP list, it could happen that not all of these IPs have been stored propperly.
⭐ New feature: Log Forwarding
It is now possible to setup a log forwarding using syslog for hostnames, who are enabled for the CDN functionality. You will then receive all access logs of that hostname at your desired target.
The configuration can be found in the basic configuration of a site.
2025.09-01
smoxy 2025.09-01 is available as of September 15, 2025.
✅ Bug fix: Fixed an issue where individual sites had multiple Basic Auth configurations, which then were no longer updated correctly. (SP-1956)
⚙️ Optimization: Various optimizations and library updates under the hood (SP-1935, SP-1942, SP-1945, SP-1947, SP-1950, SP-1957, SP-1963)
⚙️ Optimization: When copying rules in smoxy to use them in other sites, redirect sites are now hidden from the list of possible targets. (SP-1955)
🔁 Enhancement: The hostname check has been improved and now correctly evaluates hostnames even when they are running through Bunny CDN. (SP-1963)
2025.08-01
smoxy 2025.08-01 is available as of August 8, 2025.
✅ Bug fix: In some cases, the validation of hostnames starting with “www” was incorrect. This issue has been resolved.
✅ Bug fix: On the domain overview page, incorrect icons were shown for the DNS zone status. This caused confusion and the condition has been adjusted.
🔁 Enhancement: Additional validations have been added when managing SAN entries for a domain’s SSL certificate. Users are now more clearly informed about misconfigurations of invalid SAN entries.
2025.07-01
smoxy 2025.07-01 is available as of July 16, 2025.
✅ Bug fix: During the initial setup of a site, incorrect DNS records for the SSL ACME challenge were shown in the dashboard.
⚙️ Optimization: When duplicating sites, all configurations were previously copied—including Basic Auth settings. Due to differing password encryption between sites, the duplicated credentials never worked. With this release, Basic Auth users are no longer copied when duplicating a site and must be created manually.
⚙️ Optimization: When importing DNS records, entries with a TTL of 1 were interpreted as one second. Since a TTL of one second can lead to issues, such entries are now automatically imported with a TTL of one minute.
⚙️ Optimization: When setting up a new site, DNS entries for SSL issuance were shown per hostname—even when multiple hostnames required the same record. Now, only unique DNS entries are displayed.
🔁 Enhancement: If a site’s basic configuration in smoxy is set from Active to Inactive, the associated security feature will now be disabled as well. If reactivated later, the security feature will return to its original state.
🔁 Enhancement: If monitoring is configured for DNS records, those entries are now visually highlighted.
⭐ New feature: Real User Monitoring (Beta)
smoxy now includes integrated Real User Monitoring (RUM), providing real-world performance insights and load times directly within the dashboard. The feature is currently in beta and only available to organizations that have been granted beta access.
If you’re interested in joining the beta, please contact the smoxy team.
2025.05-02
smoxy 2025.05-02 will be available from May 27, 2025.
✅ Bug fix: In some cases, the total number of DNS records was counted incorrectly. We now count your entries correctly. (SP-1796)
✅ Bug fix: In some cases, the hostname context menu was unreadable when the hostname was the last entry in the table. The context menu is now always displayed correctly. (SP-1805)
✅ Bug fix: When adding new SANs in a domain’s SSL configuration, you can directly verify these entries. Unfortunately, the SAN table wasn’t updating correctly, so outdated information about your new SAN entry was still shown. Fixed. (SP-1806)
✅ Bug fix: If you’ve ever wondered why certain origin servers couldn’t be deleted, we can now assure you that in such cases you will receive an error message. In most cases, the origin server is still in use in one of your configurations. The error message will help you quickly and easily identify which configuration is using it. (SP-1807)
✅ Bug fix: A bug was fixed in SSL generation where, after adding new SANs, the SSL certificate was still being generated with the old SANs. (SP-1810 / SP-1821 / SP-1822)
✅ Bug fix: Through the API, load balancers (including their origins) could previously be deleted. Unfortunately, a check was missing to see if those origins were still in use. This ultimately caused errors on the Origin & Loadbalancer page, making it unusable for the user. Origins are now no longer deleted if they are still used by other load balancers. (SP-1829)
⚙️ Optimization: Some buttons in smoxy have been assigned new CSS classes to make styling more consistent. (SP-1530)
⚙️ Optimization: Various icons have been replaced to ensure the same icons are used for the same functions. (SP-1538)
⚙️ Optimization: We regularly scan the DNS records for all configured hostnames to give users hints on whether the configuration for these hostnames is correct. In some cases, users cannot configure CNAMEs for their hostnames. To better reflect this limitation, we’ve introduced a new status so these hostnames are no longer marked as faulty. (SP-1785 / SP-1827)
⚙️ Optimization: When activating the CDN function for a hostname, additional information has been added to the loading indicator. Longer loading times had caused uncertainty among some users. (SP-1801)
🔁 Enhancement: When using smoxy’s DNS functionality, smoxy will now send an email when the nameservers have been successfully switched. (SP-1323)
🔁 Enhancement: Since the 2025.04-01 release, you can check where your origins are used. With this release, you also see which load balancers use the selected origin server. This means you no longer have to manually search your load balancer list for your origins. (SP-1777)
🔁 Enhancement: Using the CDN? The quick action to clear the cache for a specific URL is now compatible with the CDN. (SP-1798)
🔁 Enhancement: Want to know when your SSL certificate will be renewed next? This information is now visible in the SSL configuration of each respective domain. (SP-1800)
🔁 Enhancement: When deleting a hostname, you can now simply click to copy the hostname in the confirmation popup. (SP-1809)
⭐ New feature: Are you using your own SSL certificate but want to switch to the SSL certificate generated by smoxy so you don’t have to upload a new SSL every 60 days? This is now easily possible. Go to the SSL configuration of your domain and click the button “Use Let’s Encrypt Certificate.” You will then receive a list of DNS records required for the SSL certificate. Once you have set these up, smoxy will immediately generate your new certificate and replace your old certificate after successful generation. (SP-1548)
2025.05-01
smoxy 2025.05-01 will be available from May 8, 2025.
✅ Bug fix: Closing the modal when adding a new SAN triggered a page refresh, even when no new SAN was actually added. (SP-1754)
✅ Bug fix: When generating a new user token in smoxy, the current organization was always preselected by default. This made it impossible to create a generic, organization-independent token. (SP-1769)
✅ Bug fix: An issue was fixed where updating an SSL certificate would automatically remove invalid SANs. This resulted in several subdomains no longer being covered by the certificate. Now, invalid SANs will trigger an error instead of being silently removed. (SP-1775)
✅ Bug fix: Warning and error icon popovers would no longer appear after switching browser tabs. (SP-1779)
⚙️ Optimization: Previously, new Page/Conditional Rules were always initialized with the setting “Origin and Loadbalancer”. In some cases, this led to users unintentionally overwriting their existing origin setup. From now on, no default configuration is preselected when creating new rules. (SP-1763)
⚙️ Optimization: The rule overview pages now automatically wrap lines when rule settings become very long, such as when maintaining a large cache key whitelist. (SP-1766)
⚙️ Optimization: The search function in DNS management has been improved to filter results in real-time while typing. Additionally, multiple fields are now searchable, allowing you to find entries by type, name, or value. (SP-1768)
🔁 Enhancement: Improved layout on the Domain SSL page when no SANs have been configured yet. (SP-1755)
🔁 Enhancement: The layout of the DNS management page was adjusted so that nameservers and DNS records are now shown in equally sized boxes. (SP-1756)
🔁 Enhancement: The minification process for HTML, CSS, and JS was fundamentally revised and simplified. Compression levels were removed due to issues at higher settings. The new function performs simple minification by stripping comments and unnecessary whitespace, without risking the functionality of JavaScript code. The optimization is also significantly faster now. (SP-1773)
2025.04-01
smoxy 2025.04-01 will be available from April 17, 2025. This release includes numerous bug fixes, optimizations, improvements and new features.
✅ Bug fix: Missing translations were added (SP-1743)
✅ Bug fix: The breadcrumb navigation was reviewed and adjusted on several pages to correctly reflect the actual path (SP-1750)
✅ Bug fix: Fixed an issue where the popover for hostname issues in the basic configuration of a site was not displayed (SP-1767)
✅ Bug fix: Fixed a bug where not all settings of a rule were shown. This could lead to lost settings when editing the rule. This issue only affected a very small number of customers and has already been resolved for them. All other customers were not affected. (SP-1770)
⚙️ Optimization: When creating a new site that uses the same domain as a previously deleted (but not yet permanently deleted) site, you are now asked whether to restore the old site or permanently delete it to start fresh with a new configuration (SP-1760 SP-1761)
⚙️ Optimization: The hostname validation logic and configuration checks were completely overhauled. The system now provides more accurate feedback on whether a hostname is correctly configured or if something is still missing. Many messages now include the option to trigger a recheck immediately—for example, right after a DNS change (SP-1762)
⚙️ Optimization: In the new feature for custom error pages, it was previously not possible to upload an HTML file without first enabling the feature. This restriction made little sense and has now been removed. You can now upload your own HTML files without having to activate maintenance mode first (SP-1765)
⚙️ Optimization: After setting up a new site via the wizard, there was previously no clear feedback on whether the DNS records for SSL generation were correct. This has been improved and it is now clearly indicated whether the DNS records are valid (SP-1757)
⚙️ Optimization: When importing DNS records into smoxy DNS, TTLs of 1 second are now automatically set to 1 hour. This reduces unnecessary DNS queries on every request (SP-1318)
⚙️ Optimization: When creating a new DNS entry, the most commonly used record types are now shown at the top of the selection for quicker access (SP-1319)
⚙️ Optimization: Various UI adjustments were made, such as standardizing input fields. These are purely cosmetic changes (SP-1523 SP-1524)
⚙️ Optimization: Previously, the SSL configuration could only be accessed if the CNAME records for the root domain were correctly set. This restriction has been lifted to support use cases where SSL certificates are only needed for subdomains (SP-1714)
🔁 Enhancement: The validation for response header settings has been extended to allow more special characters, making it possible to add headers like: Content-Security-Policy=frame-ancestors 'self' wp.uxturbo.de *.uxturbo.de; (SP-1245)
🔁 Enhancement: When uploading a custom SSL certificate for a domain, the Subject Alternative Names (SANs) in the certificate are now displayed on the SSL configuration page. This makes it easier to see which domains are covered by the certificate (SP-1549)
🔁 Enhancement: When a new site is created in smoxy and a root domain is provided, the hostnames for the root domain and the corresponding www domain are now automatically preconfigured. If the www domain is not needed, it can be removed with a single click (SP-1562)
⭐ New Feature: Previously, you could configure load balancers in smoxy to overwrite the hostname for each request. To avoid needing a separate load balancer for each server, hostnames can now also be overwritten at the origin level (SP-1650)
⭐ New Feature: It was previously difficult to check where in smoxy a particular origin server or load balancer was used. You can now see where each origin or load balancer is being used (SP-1645)
2025.03-03
smoxy 2025.03-03 will be available from March 21, 2025. This release introduces new features.
⭐ New Feature: Custom Pages for Errors, Security Blocks & Maintenance Mode
You can now upload custom pages as part of the basic configuration of a site. These pages will be used in the following scenarios:
• 502 & 504 Errors – When the origin server is unreachable
• Security Blocks – When a request is blocked by smoxy’s security features
• Maintenance Mode – When a site is temporarily taken offline
Yes, smoxy now supports a built-in maintenance mode! When activated, all requests will be redirected to your custom maintenance page.
Additionally, the error and security pages support custom variables that can be placed in the HTML template. These variables include:
::SX_STATUS::– The HTTP status code::SX_HOST::– The hostname of the requested site::SX_REMOTE_IP::– The remote IP address of the user
This allows for dynamic and personalized error pages, ensuring a better user experience even in unexpected situations.
⭐ New Feature: smoxy Status Page
smoxy now has its own status page: https://status.smoxy.eu
Here, you can always check the current state of smoxy and its components. The status page provides:
✅ System Status – Check if all smoxy services are running smoothly 🔧 Scheduled Maintenance Windows – Get early notifications about upcoming maintenance ⚠️ Incidents & Issues – Stay informed about ongoing and resolved problems
So if you experience delays or issues, you can quickly check the status page to see if maintenance or a system event is the cause.
2025.03-02
smoxy 2025.03-02 will be available from March 18, 2025. This release introduces two new features.
⭐ New Feature: Configurable Ignoring of Cache Tags
With this new feature, you can define a comma-separated list of cache tags that should be ignored from response headers. Tags in this list will not be set and therefore will not influence cache invalidation.
Use Case:
A common example is e-commerce platforms that automatically assign a large number of cache tags. Often, these tags are too broad, causing excessive cache invalidation when purging. As a result, the cache hit rate drops significantly. By selectively ignoring unnecessary tags, you can improve cache efficiency and prevent unnecessary purges.
⭐ New Feature: Flexible Definition of Cache-Tag Response Headers
You can now define up to four response headers from which cache tags should be extracted. By default, cache tags are read from the X-Cache-Tags header. However, since not all web applications follow the same standard, you can now specify custom header names and delimiters.
2025.03-01
smoxy 2025.03-01 will be available from March 15, 2025. This release includes numerous bug fixes, optimizations, and improvements.
✅ Bug fix: Fixed a bug when sites were duplicated, that the Origins and Loadbalancers configured in the site, were duplicated as well, instead of re-using them.
✅ Bug fix: Fixed an verification issue for the validation of a custom SSL certificate during upload.
✅ Bug fix: Previously it was not possible to define Response or Request Headers which had a value of "0". The validation for the configuration was updated.
✅ Bug fix: An exception prevented users from accepting an invitation to smoxy. It is now possible register during an invitation again.
⚙️ Optimization: When the last user of a user group is removed, this group will be automatically deleted.
⚙️ Optimization: Various descriptions and namings of settings have been adjusted to be better understandable. Settings on the basic configuration page have been re-ordered to fit thematically together and make finding configurations easier.
🔁 Enhancement: The activate smoxy button on the Dashboard of a site now shows all CNAME records that assigned hostnames should have and should make it clearer to users what DNS records to set.
⭐ New function: The site overview page got a redesign and now also shows active page and conditional rules in a tab, so you have faster access and an overview of applied rules. In addition we've added various states to hostnames that show up as warnings or error messages, if there is an issue with your hostnames. These messages will tell you what needs to be done to resolve these issues.
The search on the site overview page was improved to immediately search while typing and also highlighting hostnames that have been found by the search.
2025.02-03
smoxy 2025.02-03 will be available from February 27, 2025. This release includes numerous bug fixes, optimizations, and improvements.
✅ Bug fix: When changing the language during registration, the contents of the fields now remain unchanged. (SP-1295)
✅ Bug fix: When uploading a custom SSL certificate for a domain and the Subject Alternative Names (SAN) differ, users now receive detailed information about the changes in the entries. The new SSL certificate is only uploaded after confirmation. (SP-1621)
✅ Bug fix: Fixed an issue where not all configuration changes were applied in smoxy. This particularly affected moving hostnames between sites. (SP-1721)
⚙️ Optimization: Users with the Viewer role cannot use quick access shortcuts in the dashboard. This is now better represented by directly disabling the elements when the necessary permissions are not available. (SP-1720)
⚙️ Optimization: Removed elements from the Site Overview that were redundant if no sites had been set up yet. This includes search and filter options. (SP-1666)
🔁 Enhancement: Not exactly an enhancement, but the option to subscribe to the smoxy newsletter during registration has been removed. (SP-1670)
🔁 Enhancement: The API endpoint for deleting load balancers now also allows deleting associated origins, provided they are not used by sites or rules. (SP-1722)
2025.02-02
smoxy 2025.02-02 will be available from 19.02.2025. This release includes numerous bug fixes, optimizations, and improvements.
✅ Bug fix: Fixed an issue where the tooltip from the Traffic Widget (bottom left) would not disappear. (SP-1302)
✅ Bug fix: When going back a step in the Site Wizard, the fields were reset to their default values. Now, the wizard remembers the previously entered values when going back. (SP-1663)
✅ Bug fix: Fixed a validation issue when creating DNS records. (SP-1673)
✅ Bug fix: Fixed a display issue where the status of a DNS zone remained “Pending” even though the nameservers had already been updated. (SP-1676)
✅ Bug fix: Fixed an issue in the quick actions for cache deletion by URL, where the specified hostname in the URL was not correctly recognized. (SP-1677)
✅ Bug fix: Fixed an issue where hostnames were not correctly removed after the associated domain was deleted. (SP-1686)
✅ Bug fix: Page and Conditional Rules are now displayed in the correct order again. (SP-1699)
✅ Bug fix: Fixed an issue where SSL generation resulted in an infinite loop. (SP-1700)
✅ Bug fix: When synchronizing smoxy configurations, not all configurations were always applied. This issue has been resolved. (SP-1705)
✅ Bug fix: During the migration to the new domain management system, some domains of an organization were not displayed. Domains are now correctly displayed again. This fix is part 1. Part 2 will address the configuration of SSL certificates that contain only a SAN entry for a subdomain. (SP-1706)
✅ Bug fix: Previously deleted domains could still be selected in the DNS zones dropdown menu. This issue has been fixed. (SP-1707)
✅ Bug fix: Fixed an issue where SSL certificates were not being regenerated after new Subject Alternative Names were added. (SP-1718)
⚙️ Optimization: smoxy now automatically cleans up hostnames and SSL certificates that are not assigned to any site and therefore cannot be configured by the customer.
⚙️ Optimization: When new Subject Alternative Names (SANs) are added to a domain, smoxy automatically checks if the required CNAMEs are set and then triggers SSL generation automatically. This prevents users from forgetting to renew SSL when SANs are added. (SP-1564)
🔁 Enhancement: smoxy now regularly checks whether the CNAME records for SANs are correct and updates the status accordingly. (SP-1567)
2025.02-01
smoxy 2025.02-01 is available from February 5th, 2025. The release includes bug fixes, optimizations and a new function.
✅ Bug fix: Fixed an issue in the Site Wizard where users could access it even if they were not authorized. (SP-1631)
✅ Bug fix: Fixed a problem where the search function on the Origins and Load Balancer pages made the form for managing origins in load balancers unusable. (SP-1635)
⚙️ Optimization: In the SSL DNS entry modal, the copy button was inaccessible for very long domains (over 100 characters). Line breaks now ensure the button remains reachable. (SP-1632)
⚙️ Optimization: When creating a new site, AVIF and WebP conversion settings are now automatically enabled, ensuring that conversion is active as soon as image optimization is enabled. (SP-1268)
⚙️ Optimization: When scanning the target IP in the Site Wizard, an existing origin will now be used if found, instead of creating a new origin with the same IP. (SP-1623)
⚙️ Optimization: The overview pages for Page and Conditional Rules have been revised to display all modified settings within each rule, making rule management in smoxy easier. (SP-1647 / SP-1648)
⚙️ Optimization: Various improvements have been made to SSL generation. The process is now more stable and automatically cleans up TXT records. (SP-1672 / SP-1634 / SP-1641)
🔁 Enhancement: Preparations for CDN functionality in smoxy. (SP-1617 / SP-1618 / SP-1619)
⭐ New function: After completing the Site Wizard, a checklist is now displayed in the Site Dashboard. This helps users understand what still needs to be done to process real traffic with smoxy. The checklist disappears automatically once everything is properly configured. (SP-1633 / SP-1674)
Last updated
Was this helpful?