Claiming a port - Revision history

Bert at 15:22, 28 August 2019

2019-08-28T15:22:42Z

← Older revision		Revision as of 17:22, 28 August 2019
Line 10:		Line 10:

	[[Category:Webserver]]		[[Category:Webserver]]
			[[Category:Shell]]

Bert at 15:13, 28 August 2019

2019-08-28T15:13:51Z

← Older revision		Revision as of 17:13, 28 August 2019
Line 8:		Line 8:

	In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers.		In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers.

			[[Category:Webserver]]

Bert at 02:39, 21 January 2018

2018-01-21T02:39:37Z

← Older revision		Revision as of 04:39, 21 January 2018
Line 1:		Line 1:
	= Short answer =		== Short answer ==
	You can't, no use in trying.		You can't, no use in trying.

	= Long answer =		== Long answer ==
	We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway.		We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway.

Bert: Created page with "= Short answer = You can't, no use in trying. = Long answer = We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports...."

2018-01-21T02:35:16Z

Created page with "= Short answer = You can't, no use in trying. = Long answer = We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports...."

New page

= Short answer =
You can't, no use in trying.

= Long answer =
We do not permit aribitrary access to ports from our firewall and users are not supposed to try claiming ports. We offer classic webhosting, version control, and basic shell access. You are free to run applications, within bounds of what is reasonable, legal and ethical, on our shellservers. But they cannot claim arbitrary ports and you won't be able to access those ports anyway.

Besides the fact that this is not a service we wish to offer, it's also very hard to do this in an orderly and secure way. We would have to assign users specific ports, and check those are used correctly, furthermore proxies would be necessary for production, as no one wants their visitors to be forced to enter port numbers. Beyond that, there are tons more practical issues that would have to be solved.

In most cases, you are better off using FastCGI or CGI. We support both of these protocols, and have documentation and examples for our users on [[Using (Fast)CGI for non-PHP websites]]. If this is not what you are looking for, then we are afraid you will have to look at other services, such as VPSes, by commercial providers.