Comment by 🖥️ admin

Re: "[SOLVED?] Quite frustrated with an issue I am not really…"

In: s/self-hosted

I used the merge action to combine your post and comments into one post. You can also do this yourself when viewing a comment page (Merge into previous).

🖥️ admin

Jan 11 · 4 months ago

12 Later Comments ↓

👻 darkghost · Jan 11 at 14:54:

So yeah, port forward can only be one port. But within your local network any single company can serve on all possible ports. An antique web port waa 8080. So you can keep your port 80 forwarding to your Yunohost server and then forward port 8080 to this new service. Depends a lot on the software in your router if you can forward external port 8080 to internal <some IP address> port 80. Mine permits this, I have no idea if yours does. Then, you would access the new server externally from http://your-address:8080

I'm unsure as to the error you're getting now other than to ensure your Yunohost is set up, check ip address of it, and checking the configuration on the router.

🪐 kiyoah [OP] · Jan 11 at 15:02:

@darkghost Thank you for your response and for the additional information!

Any attempts to re-add the ports, even after changing the other server's webserver ports is now resulting in a generic error screen ever since I attempted port 80 the first time on my Debian server which started the series of errors.

I have tried a lot of things within my router's configuration, as well as re-configuring both of the servers local IPs... nothing has worked so far.

So any possibility to port forward now is completely blocked off-- so everything is offline at the moment, unfortunately :-(

👻 darkghost · Jan 11 at 15:56:

Rats! Any hope of a factory reset on the router?

☯️ leoperbo · Jan 11 at 16:31:

Did you double checked that your modem/router is giving static IP to your devices?

🪐 kiyoah [OP] · Jan 12 at 09:12:

@darkghost I did attempt to do a factory reset using the physical reset buitton on my router, though not much changed. I still got that generic error screen regardless.

@leoperbo all of my IPs are static, unless I reset it manually using "ifdown [network]" then "ifuip [network]"

Trying to manually set a local IP did make me able to port forward at least *once* (SSH), but then trying to do so afterwards for the rest sent me to that generic error screen again.

I am so clueless as to what this is.

🥬 lamb-duh · Jan 12 at 15:06:

Here are a couple steps I would recommend to gather information on the problem:

- can you connect to the servers from inside the network using the internal IP address? if you can't get to the servers from inside the network then the issue isn't with port forwarding

- is your public ip address according to your router the same ip address you see when you go to some website that tells you what your ip address is? if you see different addresses there's likely another layer of NAT imposed by the ISP, that you can't configure. Do you have a public IPv6 address? That might get around that issue

It's not surprising that tech support won't help you. ISPs don't really want you running a server from a home internet connection, even if they're selling you a service that allows it.

The button you pressed on the router is probably a power-reset, not reset to factory settings. You would find that option in the router configuration, but if you're using a router configured by your ISP they can probably do that over the phone too, if you explicitly ask to have your router factory reset.

🪐 kiyoah [OP] · Jan 13 at 00:55:

@lamb-duh

1. yes, i can connect to my servers locally, so that isn't a problem.

2. my public IP is the same no matter what, it never changes, even after restarting my router's power or "releasing" or "renewing" the IP. I have had checked via a browser and some programs that use P2P functionaility and it is the same public IP-- same for my website when it was still up. using the servers locally is not an issue, and curling the localhost still works properly.

3. the button i had pressed was a button on the back that needed to pressed with a thin object (such as a paperclip)-- which is what is often described online as the reset button; the power reset is on the front. There is also a way to reset the router to factory defaults within the router configuration itself, too-- but it did not do anything, so I might have to call my ISP regarding that.

Unfortunately I do not have IPv6 and I don't think there's a way for me to enable it within the settings-- or have a router that is capable of it.

🪐 kiyoah [OP] · Jan 13 at 06:37:

UPDATE: I have no idea what the hell I did, but it works perfectly now again? WHAT!? I left the server unplugged for about a day.

I kind of suspect that for whatever reason I was rate-limited... I don't really know if that's something that happens but yeah, this has all been quite a confusing journey for me and I have no idea how it got even fixed... seems to be a running trend with technical issues such as this.

Thanks to everyone for taking the time out of their days to try to help me as well as for the information provided... I appreciate it more than you know.

👻 darkghost · Jan 13 at 13:00:

The magic of ignoring the problem until it goes away.

🚀 jsreed5 · Jan 13 at 16:26:

Out of curiosity, what kind of router do you have? Is it issued by the ISP? To what extent do you have control over its settings? I used to be on Google Fiber, and I would sometimes run into issues where I'd change a setting but would have to wait until the router automatically restarted the necesssary services on its own. I couldn't force it, even with a power cycle. Now that I have my own router running FreshTomato, I can control everything down to the process level if I want.

🪐 kiyoah [OP] · Jan 15 at 03:10:

@jsreed5 Yeah, it's a router issued by the ISP. Now that you mention that, I am pretty sure that's what happened to me... I wanted to get a new router, but I'm not entirely sure how that would work or if there would be any limitations (I will have to do research on this myself). What is FreshTomato?

Looks like I have lots to learn...haha

🚀 stack [mod] · Jan 15 at 20:41:

I've replaced a cockmast cable modem with my own, and on another occasion, removed the verizon spyware router and replaced it with my own (leaving the fiber modem intact)... Generally you can replace the modem or at least hang your own router behind it. In the old days you had to fake the official router's NIC, but I haven't had to do that in a decade or so. Sometimes you have to somehow trigger a reset of your internet connection (using a button on the provider's web interface in your account, or asking the guy in India to reset your connection after playing 20 questions). Other times it just connects and negotiates what it needs by itself.

Original Post

🌒 s/self-hosted

🪐 kiyoah:

[SOLVED?] Quite frustrated with an issue I am not really sure how to solve... I have a Yunohost server I had been cruising with for about a month now, and I decided to add in another computer (a regular Debian 13 server) as a part of my setup. I attempted to add it using its local IP and port 80-- but I had port 80 already forwarded on my YunoHost server. I did not know at the time that this isn't something that is possible-- that returned me an error. So I thought, "simple, I just change the...

💬 13 comments · Jan 11 · 4 months ago