Reverse Proxy - Ports

[Cacsjep]

I notice that may different ACAP use same port for there webserver running in reverse proxy scenarios.

For me it would be cool to know:
All ports that can't use. Like 554, 80, 443 etc..
Which port range is suggested.

When everyone using 2001 like in examples we have may troubles.

Br Christoph

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[vivekatoffice]

Hi @Cacsjep ,
I agree with you on this. Did you get any error message after trying ports like 554, 80, 443 etc.? Or snapshot?

It may be good to add the Axis camera system used port for not using it?

manifest.json version doc: schema-field-descriptions-v1.8.0

List of Commonly used network ports.

[Cacsjep]

@vivekatoffice
Like 554 that just ports that are already used, the common used ports list was already usefull.

It would be nice if axis could tell what port range acap reverse proxy servers should use and how to prevent collision. =)

BR

[vivekatoffice]

Ya, another challenge I faced is that I had 2 ACAPs using the 2001 port. Maybe it is due to the web-server example use 2001 😄

{
	"schemaVersion": "1.8.0",
	"acapPackageConf": {
		"setup": {
			"appName": "web_server_rev_proxy",
			"vendor": "Axis Communications",
			"embeddedSdkVersion": "3.0",
			"runMode": "never",
			"version": "1.0.0"
		},
		"configuration": {
            "settingPage": "index.html",
			"reverseProxy": [
				{
					"apiPath": "my_web_server",
					"target": "http://localhost:2001",
					"access": "admin"
				}
			]
		}
	}
}

[Cacsjep]

@Cacsjep thats exactly what i mean, how could we prevent this =)

[vivekatoffice]

Hi @Cacsjep ,
This is what I got from the experts of the ACAP SDK:

Ports below 1024 are reserved for the root user, so ACAP applications won’t be able to use them. Beyond that, you are free to choose any available port. However, it’s a good idea to review the list shared here: Commonly used network ports to avoid ports already designated for specific purposes.

Using ports for reverse proxying can also be challenging since there’s no guarantee that another application isn’t already using the same port.

We will work to clarify this more thoroughly in the documentation and examples. Additionally, we hope the Axis R&D team will provide guidance and examples for using Unix sockets instead of ports, which will help prevent these conflicts.

[Cacsjep]

Thx 🙏

[apljungquist]

Getting reverse proxy with UDS to work was fairly straight forward if I remember correctly, the Rust reverse-proxy example was initially implemented using it.

The only problem was that the app has to either make the socket accessible to everyone, or be added to the www group, both of which are suboptimal from s security perspective. But now that I look at it again, I think having a TCP port seems worse 🤷