AMP Does Not Automatically Open Firewall Ports for New Instances

Technical Support
, ,
1

OS Name/Version: Debian 12
Product Name/Version: 2.6.0.6 - 20241120.1
Used Firewall: Firewalld

Problem Description:
Hi everyone!

I have noticed an issue with the AMP panel on my system. When creating new instances, the panel no longer automatically opens the required ports in the system’s firewall, as it used to.

Previously, AMP would handle this process seamlessly, ensuring that the necessary ports for new instances were added to the firewall rules. However, this behavior seems to have changed, and I now have to manually configure the firewall for each instance.

To troubleshoot, I have already restarted the server, but the issue persists.

I am unsure if this is due to a configuration error on my side, a change in AMP’s functionality, or a possible bug. Could you please advise if this behavior is intentional, or if there is a way to re-enable the automatic firewall configuration?

Best regards
Ochin

Steps to reproduce:
sudo firewall-cmd --list-all

2

Try running ampinstmgr updatefirewall as root and see what that does

3

The command returns the following error message:

[Error/1] IM was unable to execute the requested command.
[Error/1] TargetInvocationException
[Error/1] [0] (TargetInvocationException) : Exception has been thrown by the target of an invocation.
[Error/1]    at InstanceManagerCLI.Core.ExecuteCommand(List`1 Params, Dictionary`2 Args)
[Error/1] ArgumentNullException
[Error/1] [1] (ArgumentNullException) : Value cannot be null. (Parameter 'address')
[Error/1]    at ArgumentNullException.Throw(String paramName)
   at Net.IPAddress.IsLoopback(IPAddress address)
   at InstanceManagerCLI.Core.<>c.<SyncFirewall>b__79_4(PortUsage p)
   at Linq.Enumerable.WhereEnumerableIterator`1.ToList()
   at InstanceManagerCLI.Core.SyncFirewall(Boolean DryRun, IEnumerable`1 userInstances, IFirewallManager firewall)
   at InstanceManagerCLI.Core.UpdateFirewall(String SourceUser, Boolean DryRun, Boolean forceUPnPSync)
1 Like
4

Make sure that your ampinstmgr package is up to date
ampinstmgr version should print out v2.6.0.6

5

Yes, the current version of ampinstmgr is installed.

1 Like
6

Hey i seem to be having a reasonably similar issue, though all the rules for my servers are non existent now for me.
i use UFW on linux though. only since 2.6.0.6 have my rules vanished.

It all used to work, ports would be opened. NOW all of my servers ports aren’t there.
The only ones i see are 8081 with the amp tag.

8081/tcp (v6)              ALLOW       Anywhere (v6)              # AMP Management Instance
8081/tcp (v6)              ALLOW       Anywhere                     # AMP Management Instance

For now i have manually poked a hole in the port list, but idk what broke.

Also when i run the updatefirewall command, i get this error.

[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:58
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Using UFW firewall.
[Error/1] IM was unable to execute the requested command.
[Error/1] TargetInvocationException
[Error/1] [0] (TargetInvocationException) : Exception has been thrown by the target of an invocation.
[Error/1]    at InstanceManagerCLI.Core.ExecuteCommand(List`1 Params, Dictionary`2 Args)
[Error/1] ArgumentNullException
[Error/1] [1] (ArgumentNullException) : Value cannot be null. (Parameter 'address')
[Error/1]    at ArgumentNullException.Throw(String paramName)
   at Net.IPAddress.IsLoopback(IPAddress address)
   at InstanceManagerCLI.Core.<>c.<SyncFirewall>b__79_4(PortUsage p)
   at Linq.Enumerable.WhereEnumerableIterator`1.ToList()
   at InstanceManagerCLI.Core.SyncFirewall(Boolean DryRun, IEnumerable`1 userInstances, IFirewallManager firewall)
   at InstanceManagerCLI.Core.UpdateFirewall(String SourceUser, Boolean DryRun, Boolean forceUPnPSync)
7

@Mike Is there any information on this yet?

8
2 Likes
9

This is addressed in the next release.