Issue running two separate addons.

[svetlozardraganov]

Hello,

I'm developing a new version of an addon as a completely separete addon, new name, new manifest, new id, new github-repo and etc. The new addon is successfully uploaded on beamup server, but for some reason when accessing it through it's URL or Manifest it displays the other addon instead.

Here is a screenshot of both addons from the beamup-dashboard:

URLs:
https://c0a3c220c521-stremio-zamunda.baby-beamup.club/
https://c0a3c220c521-stremio-zamunda-net.baby-beamup.club/ <-- wrong addon!

Manifests:
https://c0a3c220c521-stremio-zamunda.baby-beamup.club/manifest.json
https://c0a3c220c521-stremio-zamunda-net.baby-beamup.club/manifest.json <-- wrong manifest!

Manifest IDs:
org.stremio.zamunda
org.stremio.zamunda.net

Here is the log message exerp from beamup deployment:
remote: Updating service beamup_c0a3c220c521-stremio-zamunda (id: mym718rz850dnljhv2nqauako)
remote: Updating service beamup_c0a3c220c521-stremio-zamunda-net (id: tirxye1ry1yb1cnexxthlos6t)

Why the beamup server redirects to the first addon even if I'm trying to access the second one?