FAQs

By default, Magnolia does not cache URLs with parameters, unlike Fastly, which caches them automatically. If you inspect the response headers, you may see a Cache-Control directive like:

To allow Magnolia to cache product URLs with query parameters, you need to whitelist the parameters explicitly. You can do this by modifying Magnolia’s cache configuration.

Follow these steps:

For more, see Whitelisting specific parameters.

Yes. With our premium Fastly Waiting Room feature.

For more, see Waiting room.

Yes, you can cache responses from the backend server with some slight tweaks to your Magnolia configuration.

For more on how to do this, see the article here.

To set your CDN provider to Fastly in the ingress:

With this setup, you’ll be able to whitelist the IPs necessary for Fastly to retrieve pages from the ingress.

For more on whitelisting, see Secure ingresses.

Yes.

For more on how to do this, check out the dedicated section here.

Only if you are using a headless approach with a frontend server, in this case, you will have to make sure you set the Cache-Control headers with the values you want the CDN to use.

For setups that aren’t exclusively headless, yes.

For more on this, see here.

Yes. However, this is done with an incubator module.

For more on this, see here.

Yes the following are cached by default.

You can exclude 404 errors. If you want to do this, please contact the HELPDESK.

Option 1 You can manually purge the CDN in the Cockpit.

For more details, see the Purge CDN section.

By default, CSS, JavaScript, and images are cached. Pages are not cached by default. However, you can configure your policy to cache Pages.

See Server cache policy for help with that.

Option 2 You can configure a REST Client to trigger CDN cache flushing.

For more details, see Automate flushing of CDN cache.

DX Cloud does not support JCR clustering. This is primarily for performance reasons.

Yes, you can. You can deploy as many frontend applications as you need. In fact, we have a few frontend templates to get you started.

Check them out here.

If you are upgrading Helm to version 1.14 or later and running Magnolia 6.2.44+, you must manually move the password manager keypair properties file to the expected location for the DX Cloud Helm chart.

For instructions on how to do this, see Setup: Password manager key.

By default, thumbnails are disabled to ensure optimal performance in DX Cloud. Projects with a large volume of assets per folder can cause serious performance issues when thumbsnails are enabled. If you wish to turn thumbnails back on, you can do so by setting thumbnails: true in the dam.subApps.yaml file.

For more details, see Storing assets.

To use redirects in DX Cloud, you’ll create them directly via the Cockpit if you are dealing with more than 10 redirects. If you have fewer than 10, you can manage them directly in a redirects ingress.

Yes, you can have a dedicated custom error page per site by using Virtual URI mapping. However, you should always proceed with extra caution when using Virtual URI mapping.

For more details, see Virtual URI mapping.

If SSO in DX Cloud is failing due to incorrect protocol inference, setting the port to https in the Helm chart ensures Magnolia will generate redirect URLs using HTTPS.

Yes.

However, this is done automatically.

You just need to add the certificate via the Cockpit.

Once the certificate is ready and the Fastly annotation has been correctly applied, the certificate is automatically sent and configured in Fastly.

If you need to map a domain using an A record, point the domain to the IPs associated with the load balance servers.

You can retrieve this with the following command:

Yes, you can use wildcards for custom certificates, which are handled in the Cockpit.

However, if using LetsEncrypt, you must file a Support request for wildcard certificates as of 2025-07-13.

Yes. After 15 minutes of inactivity, the user is automatically logged out of the Cockpit.

In short, no. This is not currently in scope for DX Cloud.

At the moment, we recommend that you use some of the available external services such as Mailgun, Mailchimp, etc.

The above statement is not an endorsement of any particular service, but is solely intended to provide a starting point for your mail service search.

There is technically no exact maximum to the number of concurrent authors that can be working on Magnolia on DX Cloud.

However, we recommend that no more than 50 authors work in Admincentral concurrently. This helps avoid latency issues in Admincentral due to too many authors using the Pages app, too many authors publishing, or just generally too many actions occurring simultaneously.

The latest helm chart version is 1.17.2.

As of Magnolia 6.2.59, the latest Helm chart is required for compatibility and optimal performance. We strongly recommend always deploying the latest Helm chart to leverage enhanced stability, security updates, and streamlined configuration management.

For detailed guidance on Helm charts and the values.yml file, refer to Helm values.

The minimum Helm chart version needed for Magnolia 6.3 is 1.15.0.

You upgrade your version in the .gitlab-ci.yaml file.

The latest helm chart version is 1.17.2.

For more on Magnolia 6.3, see Magnolia 6.3.

You need to create an ingress for each public.

See Creating an ingress for steps on how to do that.

You update the Helm chart version in the .gitlab-ci.yaml file. You must modify the version, the values file, and the namespace. Pipeline configuration may vary by customer implementation; though we do provide blueprints. Ensure you adapt the configuration accordingly to fit the project requirements.

For DX Cloud, you bootstrap your license in your project values.yml file provided to you at the start of your project.

Your license key is entered in the values.yml file during onboarding for DX Cloud, so you don’t need to worry about entering it to get started.

However, you may need to update your license at some point. For example, when your license expires, you need to update to a license that isn’t expired. In this case, you should update your license key directly within Magnolia instead of the values.yml file.

For steps on how to do this, see Updating a license key.

Sticky sessions, or session persistence, is when you instruct the load balancer to remain linked to a specific node (server) to avoid losing the session data if the request goes to the other server. Essentially, you send the request from a given IP to the delivery server, but continue to send follow-up requests to the same server until the session expires. Session persistence is needed when the project has transactions or required data in the session.

Sticky sessions are typically used in situations where you have some data in the session and the sessions are not replicated between servers, but you also need to ensure that the data doesn’t get lost.

To enable sticky sessions:

You can define custom environment variables in the Helm Values file in your project.

Yes you can.

The Fastly maintenance page is at the CDN level. To use this approach, reach out to the Helpdesk for assistance.

The re-creation of the key pair must be done on the author instance.

When using DX Cloud, the keys are automatically distributed to the public instance with the help of a dedicated sidecar.

Currently, the minimum supported Java version for DX Cloud is Java 11 (LTS).

DX Cloud does not support autoscaling. You must scale up or down by changing the replicas value.

You can add a public instance in the values.yml file or in the Cockpit.

The recommended base image is:

This is defined in the image.tomcat.tag helm value. For more, see Helm values.

No.

DX Cloud is a solution designed to deploy Magnolia only. In some instances, headless frontends are also deployed as part of DX Cloud.

We don’t allow custom helm charts or operators for DX Cloud.

Only the official DX Cloud helm chart is used for deployments. Certain properties in the values.yml file which is created during setup can be configured. However, only those properties available in the official DX Cloud Helm chart are available at all.

The latest helm chart version is 1.17.2.

Yes, you can.

For more on this topic, see Multicluster environments.

Yes, you can.

For more on this topic, see Multicluster environments.

The latest maven archetype version for the cloud bundle is 1.10.

By default, your database and application will scale if you are performing the action in the Cockpit.

However, if you notice the database isn’t scaling, check your helm values.yaml file to ensure the following are set to true:

For more, see Helm Values reference.

Of course, there could be a number of a reasons why your DX Cloud application is slow to start.

It could be that you need to enable startupProbe in your values.yml file to accommodate a large amount of storage or if you’re migrating to DX Cloud.

This applies to both magnoliaAuthor and magnoliaPublic.

After indexing is complete, you should revert the startupProbe to the default settings.

For more on this topic, see Helm values.

You can restrict access to your site in a couple of different ways:

For more details, see CDN settings.

Yes, 2FA is used for all customer and partner accounts.

To prevent and mitigate DDoS attacks, DX Cloud grants all customers (using Fastly as their CDN):

What if I’m not using Fastly?

WAF Intro

Web Application Firewalls, or WAFs, protect web applications from common malicious attacks such as cross-site-scripting (XSS) and SQL injections. Essentially, they act as a type of wall or shield between your web application and the internet. If you have your own CDN for your project, you’ll likely have your own WAF.

If you choose to go with the default CDN for DX Cloud, you’ll be protected with the Fastly WAF.

The Fastly WAF inspects the web traffic at the HTTP application layer by looking at all HTTP and HTTPS requests (both header and body included). This can be configured specifically for your deployment.

What happens if attacks are detected?

If the WAF detects any of the owasp or application-multi attacks, it automatically blocks the request. If they detect there is an increased volume of requests, Fastly notifies us at Magnolia, and we perform a security review.

If needed, we send the logs to you to check if the requests have come form the same IP and if the requests are legitimate or not. If you need to block the IP, you can do it through the cockpit.

We encourage you to use the cockpit. However, if you feel you need to, you can request our help directly with the issue.

See Web Application Firewall (WAF) for more details.

There are three levels of control when REST requests are issued:

Permissions to issue REST requests are controlled using Magnolia’s standard role-based security mechanism.

The rest-anonymous role is handled differently in DX Cloud than in on-prem Magnolia.

For more details on rest security generally for Magnolia, see REST security.

Generally, no. You should only use configuration and/or server snippets exactly as instructed by documentation or the DX Cloud team. Making changes to these snippets without consultation or approval could lead to unintended consequences for your PaaS project.

No. As stated in Is it okay to use ingress-nginx snippets?, we generally advise against using nginx-ingress configuration and server snippets and you should only use it exactly as instructed by the documentation or the DX Cloud team.

For redirects, use our Redirects feature in the Cockpit.