Skip to content

Allow App Access to Protected Stores

A development or staging store may have an extra password prompt, an IP restriction, or a browser verification page in front of Shopware. These protections can block Improved Import, Export & Mass Actions, even when you can open the store in your browser.

Ask your hosting provider or administrator to allow the app’s requests through this extra protection using the source IP below. This is also called IP allowlisting or whitelisting.

SettingValue
Source IPv4 address174.138.100.130
If the provider requires CIDR notation174.138.100.130/32
DestinationYour store’s HTTPS hostname, normally port 443
PurposeRequests from the hosted Firebear app to your Shopware store

This is the outbound IP of our production hosted app, including when you use that app with your development or staging store. It is not your store’s IP or your own computer’s IP. The /32 suffix means a single IPv4 address.

Your browser may remember a hosting password or an access-gateway login. Import and export requests come from Firebear’s servers, not from your browser, so they do not share that session. The app cannot complete an interactive login or CAPTCHA.

Possible symptoms include HTTP 401 or 403, a password prompt or HTML login page instead of an API response, and failures when requesting an API token. These symptoms can also have other causes; an error code alone does not prove that a firewall is blocking the app.

Ask Your Hosting Provider to Add an Exception

Section titled “Ask Your Hosting Provider to Add an Exception”
  1. Identify the hostname used by the app, for example staging.example.com. It must resolve publicly and be reachable over HTTPS. Allowlisting does not make a local-only or VPN-only store reachable.
  2. Open your hosting panel’s settings for password protection, allowed IPs, or access rules. If you do not manage these settings, send the request below to your hosting provider.
  3. Add 174.138.100.130, or 174.138.100.130/32 if required, as an allowed source for that store. Limit the exception to the affected hostname.
  4. Ensure the matching requests can reach the Shopware Admin API, including /api/oauth/token and the other /api/ endpoints used by imports and exports. If the store is installed under a subdirectory, include that prefix. Allow the API’s required HTTP methods, not only browser GET requests.
  5. Exempt those requests from the additional password prompt or interactive browser challenge. A network firewall allow rule alone does not bypass HTTP Basic Authentication. Keep the additional protection for other visitors.
  6. If you use a CDN, reverse proxy, or a service such as Cloudflare Access, check that layer too. A firewall/WAF exception does not necessarily bypass a separate access-login policy. Your provider must use the real client IP supplied by a trusted proxy, rather than trusting arbitrary forwarded headers.

We use Firebear’s Improved Import, Export & Mass Actions app for Shopware 6. Please allow source IPv4 174.138.100.130/32 to access our store at https://staging.example.com over HTTPS. For this source and hostname, please bypass the additional hosting password or interactive access challenge so the app can reach /api/oauth/token and the other Shopware Admin API endpoints under /api/. Keep Shopware’s API authentication and permissions enabled, and keep the additional protection for other visitors. Please check both the proxy/CDN and the origin server rules.

Replace https://staging.example.com with your actual store URL before sending.

  1. Open the app in your Shopware Administration.
  2. Run a small export first and confirm that it finishes and the file can be downloaded.
  3. If you use imports, run a small import with known test data in your staging store and verify its result and progress updates.
  4. If a request is still blocked, ask the provider to inspect access logs for source 174.138.100.130 at the time of the failed job. The browser working on your computer does not verify access from the app.

If authentication still fails after the request reaches Shopware, check the Shopware API credentials and app permissions. Do not widen the IP exception to all visitors to fix a credentials error.

Follow Create a Support Ticket. Include your store URL, job/profile name, the error message, the time and time zone, and which password protection or proxy you use. Include the provider’s findings if available. Do not send passwords, API secrets, or access tokens.

For installing the app on a separate test shop, see Staging and Go-Live.