Redirecting a port to a web page.


Recommended Posts

hi,

I recently set up my first server and I would like to know how I can redirect a localhost:8022 to my Ip/domain name address such as

192.168.1/ajaxterm or domain.com/term

I'm using the latest version of debian and on a ppc if thats any help?

also if not any hassle can i be told in a step by step way please im a linux newb so i need to simpleton stuff :p

Link to comment
https://www.neowin.net/forum/topic/643463-redirecting-a-port-to-a-web-page/
Share on other sites

hi,

I recently set up my first server and I would like to know how I can redirect a localhost:8022 to my Ip/domain name address such as

192.168.1/ajaxterm or domain.com/term

I'm using the latest version of debian and on a ppc if thats any help?

also if not any hassle can i be told in a step by step way please im a linux newb so i need to simpleton stuff :p

This is what I would do:

Install and configure Apache web server.

Open firewall port.

Create an index page to redirect users to the new website.

Okay, I don't normally use debian, so I am not extremely familiar with the structure, and I don't know if this is the "best" way to do this, but I would do it like this:

1) Login as root:

su -

2) Download the source code for Apache web server from:

http://download.filehat.com/apache/httpd/httpd-2.2.9.tar.gz

wget http://download.filehat.com/apache/httpd/httpd-2.2.9.tar.gz

3) Decompress and extract source:

gzip -d httpd-2.2.9.tar.gz

tar -xvf httpd-2.2.9.tar

4) Configure, make, make install (build the source for your environment)

cd httpd-2.2.9

./configure

make

make install

5) Apache web server is now installed, we need to configure the port.

cd /etc/httpd/conf/

vi httpd.conf

Here you must edit Apache's configuration file, and set it to listen on the correct port.

Change the line that reads: "Listen 80" to "Listen 8022" or whatever port you want.

You can make changes to the file by first pressing "i" to enter into VI's edit mode.

To save, hit ESC to return to command mode and type "wq".

6) Create a new index.html page.

vi /var/www/html/index.html

Edit the page to have this HTML:

<html>
<head>
<meta http-equiv="refresh" content="0;url=https://www.neowin.net/">
</head>
<body>
This page has moved to <a href="http://neowin.net/">http://neowin.net/</a>
</body>
</html>

Save the file the same way as before.

7) Alter your firewall rules.

This step is platform and install specific.

If your using gnome and iptables click on System -> Administration -> Firewall.

Open up port 8022.

8) Start/Restart Apache web server.

/etc/init.d/httpd restart

Thats it.

Hope it works for you.

This is what I would do:

Install and configure Apache web server.

Open firewall port.

Create an index page to redirect users to the new website.

Okay, I don't normally use debian, so I am not extremely familiar with the structure, and I don't know if this is the "best" way to do this, but I would do it like this:

1) Install Apache2

sudo apt-get install apache2

2) Apache web server is now installed, we need to configure the port.

cd /etc/apache2

vi apache2.conf

Here you must edit Apache's configuration file, and set it to listen on the correct port.

Change the line that reads: "Listen 80" to "Listen 8022" or whatever port you want.

You can make changes to the file by first pressing "i" to enter into VI's edit mode.

To save, hit ESC to return to command mode and type "wq".

3) Create a new index.html page.

vi /var/www/index.html

Edit the page to have this HTML:

<html>
<head>
<meta http-equiv="refresh" content="0;url=https://www.neowin.net/">
</head>
<body>
This page has moved to <a href="http://neowin.net/">http://neowin.net/</a>
</body>
</html>

Save the file the same way as before.

4) Alter your firewall rules.

This step is platform and install specific.

If your using gnome and iptables click on System -> Administration -> Firewall.

Open up port 8022.

5) Start/Restart Apache web server.

/etc/init.d/apache2 restart

Thats it.

Hope it works for you.

Save yourself the trouble of compiling :)

Save yourself the trouble of compiling :)

I wasn't sure if aptitude was installed by default on Debian systems so I went with the compiler.

Thanks, that certainly makes it a lot easier.

Just a quick question about it though.

Without using sudo for each step he won't be able too:

1) Edit apache's configuration file: /etc/apache2/apache2.conf

2) Change anything in /var/www/

3) Restart the apache2 daemon

...right?

Why not just use 'su -'?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The proportion (or number of iterations) has nothing to with this aspect of Copyright I am describing. In short, it doesn't matter how many times the manager tells you to change something or how. Your work product is always YOURS until and unless you then assign that to the person representing the client/company, usually for financial compensation -- either in salary or as a subcontract work for hire payment. if iterations determined copyright, then businesses would have learned to just keep making changes until they could claim they owned the copyright, without having to compensate the artist for their work. And that would be BAD. The only place where the amount of changes does have a role is in how much does a human modify a previous public domain work (from any source) before it is considered fair use or their own work, etc. For example, if a human makes substantial changes to a public domain (re: AI, by definition) work, then they can then claim that derivative work as their own...but NEVER the original version, of course. That's why anyone can make a movie about Dracula, for example, as long as it is based on the public domain novel, but not if they take new ideas from copyrighted movies made afterwards. As one of the people who personally advised the US Copyright Office on their recent ruling on these very issues, be assured that I specifically used the terminology precisely -- though I made it simple enough for laymen to understand it. If I made this confusing by doing so, I apologize. But, to be clear regarding your assumption that I would agree to your second statement that I quoted above -- the answer is NO. If AI does the work, no matter how much "direction" you give it, it cannot be copyrighted. All AI generated content is in the Public Domain and therefore the copyright cannot be assigned to ANYONE, even you -- until and unless substantial modifications are made to it BY A HUMAN BEING (yourself or a contracted artist/writer/etc.) and then that copyright on the derivative work is legally (in writing) transferred to you. This is a critical distinction. And it is important that people, especially AI sloppers, understand this. For example, YouTube is not paying AI slop generators for the copyright, etc. of their AI slop. What YouTube is doing is sharing AD REVENUE for permission to publish your AI slop. Copyright/ownership/rights never come into it. Importantly, that means that anyone can copy any AI slopware on YouTube, etc. and rehost it anywhere they want, even back on YouTube, and there is nothing legal that YouTube can do about it with regards to copyright protections, ownership, DMCA, etc. Anyone is legally free to use any AI slopware in any way they want. When this ruling was pending, I warned Disney legal of all of this before they did their OpenAI deal -- that it would literally dilute their entire IP portfolio forever. They ignored that warning for the PR and stock bump. But that is why, when the ruling came down last year, Disney quickly extricated themselves from that OpenAI deal, even eating the initial upfront fees -- followed closely by OpenAI ending their entire AI video generating business model. They adjusted their PR release dates to make this less obvious to shareholders, of course. Phew. I hope that this clears up the key distinctions for you and anyone reading. If you have any additional questions or even hypotheticals about AI and Copyright, please feel free to ask.
    • Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. About time.
    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      576
    2. 2
      +Edouard
      188
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      78
    5. 5
      neufuse
      72
  • Tell a friend

    Love Neowin? Tell a friend!