# Troubleshooting — GivEnergy Insight 1.4.0 for Synology

## The package will not install

- Confirm DSM is 7.1 build 42661 or newer.
- Confirm the NAS uses Synology `x86_64`, not ARM.
- Install Node.js v18 from Package Center.
- Verify the SPK checksum.
- Use Package Center → Manual Install.
- If DSM says the package uses a resource exclusively for Synology packages,
  the selected installer is version 1.3.7 or older. Install 1.4.0 or
  newer, which does not request that resource.

## “Failed to start GivEnergy Insight”

Confirm Node.js v18 or v20 is installed. Restart the package and inspect:

```text
/var/packages/GivEnergyInsight/var/givenergy-insight.log
```

Do not share the log publicly until local IP addresses and serial numbers have
been reviewed.

## “Sorry, the page you are looking for is not found”

Open the package from the DSM application menu. For a direct link, use:

```text
http://NAS-IP:5000/webman/3rdparty/GivEnergyInsight/index.cgi?runtime=dsm
```

For HTTPS, change the scheme and DSM port to `https` and `5001`.

## The page loads but cannot reach the service

Use the DSM-mode URL:

```text
http://NAS-IP:5000/webman/3rdparty/GivEnergyInsight/index.cgi?runtime=dsm
```

Refresh the page without cache after an upgrade. The `/givenergyinsight/` path
belonged to older DSM 7.2-only builds and is not the compatibility address for
1.4.0.

Never browse directly to port `43819`; it accepts loopback connections only.

## DSM sign-in is required even though DSM is open

- Confirm DSM and the app are opened with the same hostname, scheme and port.
- A login on the NAS private IP does not authenticate the public IP or DDNS name.
- Use **Already signed in to DSM? Check this browser session**.
- Otherwise sign in through the app portal.
- Enter the Synology Secure SignIn verification code when two-factor
  authentication is enabled.
- Allow cookies for the NAS address.

## “This local service only accepts requests from the app on this computer”

This normally indicates the page opened from an older direct-service address or
a cached old build. Upgrade to 1.4.0, open it from the DSM application
menu or use the full `/webman/3rdparty/GivEnergyInsight/index.cgi?runtime=dsm`
path, and refresh without cache.

## Remote DSM works but the application does not

Use:

```text
http://ExternalIP:ExternalPort/webman/3rdparty/GivEnergyInsight/index.cgi?runtime=dsm
```

Confirm the router forwards that external port to DSM port 5000, or preferably
forward an HTTPS port to DSM port 5001. Do not create a separate forwarding rule
for app port 43819.

## The Remote Access test fails

- Confirm the generated hostname and external port match the router rule.
- For HTTPS, forward the selected external port to NAS TCP port `5001`.
- Confirm DSM HTTPS is enabled and the hostname has a valid certificate.
- Test from a phone with Wi-Fi disabled; a home router may not support NAT
  loopback.
- A test made from an HTTPS page cannot probe an unencrypted HTTP address.
- QuickConnect cannot carry this third-party package route. Use DDNS, a direct
  DSM HTTPS address or a VPN.
- Never forward inverter port `8899` or internal app port `43819`.

## The public address works outside but not at home

The router may not support NAT loopback/hairpin NAT. Test with phone Wi-Fi
disabled, use the NAS private address at home, or configure split DNS.

## No inverter is discovered

- Confirm the NAS and inverter are on the same routed private network.
- Enter the inverter IP manually.
- Allow NAS-to-inverter TCP port 8899 through VLAN/firewall rules.
- Stop another service that exclusively owns the inverter connection.
- Confirm the communication dongle exposes the compatible local interface.

## Live data stops

- Confirm the package is Running in Package Center.
- Check that the inverter IP did not change; reserve it in DHCP if necessary.
- Disconnect and reconnect the saved inverter.
- Compare with the dummy inverter to separate package and hardware problems.

## Information to include with a problem report

- NAS model
- DSM version and build
- GivEnergy Insight version
- Local or remote URL format, with public IP removed
- Whether dummy mode works
- Inverter generation and dongle type
- Scan or manual-IP connection
- Exact error message
- Relevant redacted log lines