F5F Stay Refreshed Power Users Networks What you need to do is forward the port for your service.

What you need to do is forward the port for your service.

What you need to do is forward the port for your service.

A
AmberDawson
Junior Member
9
03-25-2016, 03:19 AM
#1
Hello. To forward a port for your web server, first identify the specific port number it uses. Once you know the port, you can configure your router or firewall to redirect incoming traffic to that port. For the URL 192.168.1.xx/multicraft, check its documentation or settings to confirm the correct port and steps needed.
A
AmberDawson
03-25-2016, 03:19 AM #1

Hello. To forward a port for your web server, first identify the specific port number it uses. Once you know the port, you can configure your router or firewall to redirect incoming traffic to that port. For the URL 192.168.1.xx/multicraft, check its documentation or settings to confirm the correct port and steps needed.

J
Johnnyy6
Junior Member
41
04-12-2016, 11:36 AM
#2
Multicraft operates from a private IP address, so it makes sense to open port 80 publicly and point it to your external IP. Your ISP probably blocks direct access to port 80 because they don’t want users hosting servers through them. A workaround is to forward another port—like 8080—to port 80, allowing you to reach the service via a different number. This means accessing the interface at "your.external.ip/8080/multicraft". You’ll also need to configure your router to forward the necessary ports (such as 443 for HTTPS) to the Raspberry Pi’s IP address. Only port 443 should be forwarded if you intend to enable encryption, as most ISPs block these common ports. It’s important to note that incoming traffic on these ports is often blocked by your ISP to prevent unauthorized hosting. Instead of relying on default settings, route an arbitrary external port to the internal port 80 or 443 on the Raspberry Pi. For example, in a screenshot you can see external port 5000 directed to internal port 80. When connecting to the WOL server later, you’ll have to specify the correct port, such as wol.example.com:5000. Adjust the ports accordingly for any services you wish to reach remotely.
J
Johnnyy6
04-12-2016, 11:36 AM #2

Multicraft operates from a private IP address, so it makes sense to open port 80 publicly and point it to your external IP. Your ISP probably blocks direct access to port 80 because they don’t want users hosting servers through them. A workaround is to forward another port—like 8080—to port 80, allowing you to reach the service via a different number. This means accessing the interface at "your.external.ip/8080/multicraft". You’ll also need to configure your router to forward the necessary ports (such as 443 for HTTPS) to the Raspberry Pi’s IP address. Only port 443 should be forwarded if you intend to enable encryption, as most ISPs block these common ports. It’s important to note that incoming traffic on these ports is often blocked by your ISP to prevent unauthorized hosting. Instead of relying on default settings, route an arbitrary external port to the internal port 80 or 443 on the Raspberry Pi. For example, in a screenshot you can see external port 5000 directed to internal port 80. When connecting to the WOL server later, you’ll have to specify the correct port, such as wol.example.com:5000. Adjust the ports accordingly for any services you wish to reach remotely.

E
Erual
Member
66
04-14-2016, 04:05 AM
#3
I've attempted this on my DreyTek Vigor2830n V2, but the system warns that the value of the start port cannot exceed the end port. Edited: I just realized this was four years ago.
E
Erual
04-14-2016, 04:05 AM #3

I've attempted this on my DreyTek Vigor2830n V2, but the system warns that the value of the start port cannot exceed the end port. Edited: I just realized this was four years ago.