FAQ & Troubleshooting

FAQ & Troubleshooting — Code Management

Below are answers to common problems developers may face when managing or running code.

Port Already in Use

Error: Port 3000 is already in use

Solution:

Find the process using the port:
```
lsof -i :3000
```
Kill the process (replace <PID>):
```
kill -9 <PID>
```
Or change the port in your .env or config:
```
PORT=3001
```

Permission Denied (File or Directory)

Error: EACCES: permission denied, open 'file/path'

Solution:

Check file or folder permissions:
```
ls -la file/path
```

Change ownership or add permissions:

sudo chown -R $USER:$USER file/path
chmod +rw file/path

Avoid using sudo to start dev servers unless necessary.

Git Push Rejected

Error: [rejected] main -> main (non-fast-forward)

Solution:

Pull the latest changes first:
```
git pull origin main --rebase
```
Resolve conflicts (if any), then:
```
git push origin main
```

Changes Not Reflected After Build

Why are my changes not showing up?

Possible Causes: - Cache issues - Build server not watching the file - Wrong import path

Solutions: - Restart the development server - Clear browser cache or try in Incognito mode - Verify the file is saved and properly imported

Environment Variables Not Loading

Error: Environment variables undefined

Solution:

Ensure .env file exists with:
```
DB_USER=myuser
DB_PASSWORD=securepass
```
Use a loader (e.g., for Node.js):
```
require('dotenv').config();
```
Restart the app after making changes to .env
Ensure .env is not accidentally committed (add it to .gitignore)

Open App Not Working in Code Management In Qlik Enterprise

Issue: Open App is not loading or showing a blank screen

Cause:

This issue occurs when required security headers are not configured in Qlik Sense Enterprise, or when external domains are blocked by CSP restrictions.

Solution:

Step 1: Update Virtual Proxy Headers (QMC)

Open Qlik Management Console (QMC)
Go to Virtual Proxies
Select the active virtual proxy
Navigate to Advanced
Locate Additional Response Headers

Add the following:

X-Frame-Options: SAMEORIGIN;
Content-Security-Policy: frame-ancestors 'self' https://hostname.domain:4040; connect-src 'self' https://hostname.domain:4040;
Access-Control-Allow-Origin: https://hostname.domain:4040;
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

Step 2: Update Code Management Server Configuration

Open Code Management server settings
Locate PRODUCTION_ORIGIN configuration
Add all required external domains (IIS, firewall, reverse proxy origins)

This ensures external domains are not blocked by CSP restrictions.

Open App Not Working in Qlik SaaS

Issue: Open App not loading or showing blank screen

Cause: Qlik SaaS login (https://login.qlik.com/) cannot be displayed inside an iframe.
Also, if the Code Management domain is not allowed in CSP settings, the app will be blocked.

Solution:

Log in to Qlik Cloud in a separate browser tab before opening the app
Add the Code Management domain in:
- Qlik Cloud → Administrator → Content Security Policy
Update PRODUCTION_ORIGIN in Code Management settings to include:
- Code Management domain
- Qlik Cloud domain
- Any external (IIS / firewall / proxy) domains

Result: The app loads inside Code Management using the active session.

Note: If you are using a custom gateway or domain, ensure it is also allowed in CSP and added to PRODUCTION_ORIGIN.

Application Not Working After Domain or Port Change

Issue: App not working after updating domain, port, or URL

Cause: When the domain or port is changed, existing IDP (Identity Provider) and authentication routes still point to the old URL.

Solution:

Update IDP configuration with the new domain and port
Update all authentication routes/endpoints
Ensure all services and redirect URLs use the updated values

🛠 Still Stuck?

Check the console or server logs for more specific errors. If the issue persists, contact the DevOps or Infra team with logs and steps to reproduce the issue.