Community discussions

MikroTik App
 
Nyxiality
just joined
Topic Author
Posts: 4
Joined: Wed Aug 02, 2023 6:10 pm

Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 6:20 pm

Brand new to using RouterOS, so please be gentle.
I'm hosting a website on 192.168.88.209:80, and I have set up records on Cloudflare that point to it. However every time I try to go to it, it comes up with the Mikrotik login page. This happens on every device, local or not. Even my friends say they see the login page.

I've tried changing Apache to use Port 81, then forwarding port 80 to 81, which yeilded the same results.
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 2978
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 6:24 pm

Last edited by BartoszP on Wed Aug 02, 2023 6:41 pm, edited 1 time in total.
Reason: edited
 
Kevdevon
just joined
Posts: 13
Joined: Fri Jul 07, 2023 12:55 pm

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 6:30 pm

Brand new to using RouterOS, so please be gentle.
I'm hosting a website on 192.168.88.209:80, and I have set up records on Cloudflare that point to it. However every time I try to go to it, it comes up with the Mikrotik login page. This happens on every device, local or not. Even my friends say they see the login page.

I've tried changing Apache to use Port 81, then forwarding port 80 to 81, which yeilded the same results.
Is 192.168.88.209 the client? Are you forwarding the external IP address to this machine using DSTNAT?
If so, trying moving the Mikrotik interface off port 80 or disable if if you don't need it (using Winbox or command line).
 
Nyxiality
just joined
Topic Author
Posts: 4
Joined: Wed Aug 02, 2023 6:10 pm

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 6:45 pm

Brand new to using RouterOS, so please be gentle.
I'm hosting a website on 192.168.88.209:80, and I have set up records on Cloudflare that point to it. However every time I try to go to it, it comes up with the Mikrotik login page. This happens on every device, local or not. Even my friends say they see the login page.

I've tried changing Apache to use Port 81, then forwarding port 80 to 81, which yeilded the same results.
Is 192.168.88.209 the client? Are you forwarding the external IP address to this machine using DSTNAT?
If so, trying moving the Mikrotik interface off port 80 or disable if if you don't need it (using Winbox or command line).
x.x.88.209 is where the website is hosted. Is this the correct code to do what you suggested?
/interface ethernet disable ether1
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 2978
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 6:48 pm

Try to read and implement HarpIn NAT as in link.
 
Nyxiality
just joined
Topic Author
Posts: 4
Joined: Wed Aug 02, 2023 6:10 pm

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 6:55 pm

Try to read and implement HarpIn NAT as in link.
I'm not really bothered about being able to access it on my own end, its that its also showing the same thing for everyone trying to access it externally.
 
erlinden
Forum Guru
Forum Guru
Posts: 2627
Joined: Wed Jun 12, 2013 1:59 pm
Location: Netherlands

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 8:10 pm

You might want to share your config, so we can solve this:
/export file=anynameyoulike
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 21904
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: Forwarding Port 80 leads to the login page, not website

Wed Aug 02, 2023 8:17 pm

As stated we need facts.
/export file=anynameyouwish ( minus router serial number, public WAN IP information ).

viewtopic.php?t=179343
 
Nyxiality
just joined
Topic Author
Posts: 4
Joined: Wed Aug 02, 2023 6:10 pm

Re: Forwarding Port 80 leads to the login page, not website  [SOLVED]

Tue Aug 08, 2023 6:09 pm

Hi all, sorry for the big wait. This problem is solved now. Turns out it was a DNS record that was wrong.

Who is online

Users browsing this forum: pts0, WarlorZ and 32 guests