S
S
Studentka19962020-10-07 13:40:53
linux
Studentka1996, 2020-10-07 13:40:53

Why doesn't the new site address work?

I did everything according to the description of Lab No. 6, the only thing I couldn’t install was the libapache2-mod-fastcgi package.
In general, all pages are displayed correctly, but instead of the ip from the previous Lab, the page address should be: karina.stankin:8080/index.html

Piece of Lab 6: The next task pool is related to configuring Nginx as a reverse proxy to Apache. Install the required packages:
5f7d9ab7979d5579145762.png
5f7d9ad3753a0254465570.png
5f7d9b0cc1664565634722.png

Files:
5f7d99e81d508357596206.png
Default:
5f7d9c3a94e24173700524.png

Incorrect:
5f7d9bcde4a70856453197.png
Correct: I double-checked
5f7d9a033bb92278339909.png

, everything is correct, but why doesn't it work :( Please help.
It is necessary to display pages at karina.stankin:8080 instead of 172.20.10.8

SOLUTION:
The correspondence between the address and the domain really helped (Line 172.20.10.8 karina.stankin written in the hosts file) and the file name is not index.html but index.htnml (that's why the page didn't work)
5f7dbd88c203a953601562.png

Answer the question

In order to leave comments, you need to log in

1 answer(s)
H
hint000, 2020-10-07
@Studentka1996

well dyk your DNS is not configured. How does the computer find out the address karina.stankin? Nowhere. In the outside world, TLD stankin is not registered. So you should have DNS on the local network, and configure it. The web server is not to blame for this problem, leave it alone for now.
PS You can, of course, register in the hosts file. Such a crutch is easier.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question