Trouble with HTTPD Continued

Support
1

Hi noam-alum,

The system did not let me send a reply so I started a new thread.

The way I access the website through my browser is as follows:

I created an AlmaLinux 9 instance at Linode. Linode provides you with a Public IP Address. I can ssh into the instance using its address. For example:

ssh root@51.117.55.68

I can also access the site through my browser. For example, I type this into the address bar in Google Chrome:

51.117.55.68

I am continuously running my test web page in my browser now.

I should easily be able to run my Fastapi application in this manner. Since I am not I have to go through all of these machinations.

This is the configuration file I am using which I have named app.conf:

The output of systemctl status httpd looks fine.

Whenever I make changes to the files at /etc/httpd/conf.d and check my browser’s reaction, I get different kinds of error message output.

Thanks again.

2

This is my configuration file:

<VirtualHost *:80>
ServerName 51.117.55.68
ServerAlias

ProxyPreserveHost On
ProxyPass / http://127.0.0.1:8000/
ProxyPassReverse / http://127.0.0.1:8000/

<VirtualHost *:443>
ServerName 51.117.55.68
ServerAlias

ProxyPreserveHost On
ProxyPass / https://127.0.0.1:8000/
ProxyPassReverse / https://127.0.0.1:8000/

I commented out the line for the logs as they were causing issues.

3

The issue is with the ServerName and ServerAlias, please read my earliest reply again and you would see that you cannot use an IP address in the ServerName but a valid domain.
Keep in mind that if the domain is not registered and configured to point to your server you have to use a hosts file manipulation to access the website as I’ve stated here.
Also I’m not sure if you sent the full configuration file but if so there should be a closing tag to VirtualHost that looks like this

</VirtualHost>

After every change to the https configuration files you have to reload/restart httpd

systemctl restart httpd
# or
systemctl reload httpd

I request from you to review our earlier messages and confirm you are using the guidance I supplied for you.

4

Thanks Noam,

I had to leave certain parts out of my last post because this site is complaining that as a new user I am not allowed to use more that 2 attachments in my posts and did not allow me to post. I had to omit a lot of pertinent information to just be able to post. They aren’t making it easy for me here.

Yes. I keep restarting HTTPD each time and I am no longer getting any error messages from this process.

As far as a valid domain, I don’t have one. I’m using the Linode IP Address because I don’t have a valid domain name.

I have been working with Linode support on some issues to try to get Fastapi up and running on a Debian 10 image running NGINX alongside this one and I’m running into issues with that too. Linode put out a tutorial on this and I complained that the steps the developer was using weren’t working. It would not allow me to install Fastapi. Linode support found out it was an issue on their end.

At no point did they tell me I needed to use a valid domain name. I’ll ask them if the process is different when I’m running HTTPD on AlmaLinux 9.

I’ll go back and make sure I can follow what you have posted previously if it’s possible to implement.

Thanks again.

Steve

5

When I say valid domain name it doesn’t need to be registered just be an actual domain like expample.com then you can access it directly using a hosts file manipulation.

6

Thanks. I’ll have to ask Linode how to do that because I don’t know.

7

I’ve sent to you twice already how to do so here.

8

Sorry. I didn’t see this earlier or if I did I overlooked it.

When I look in /etc/hosts I see a bunch of information in there. Am I supposed to overwrite that information? Should I tell you what is there now?

What is my domain?

I know the IP address

Thanks again

9

You can choose what ever domain you’d like, for example smitsky.com as the domain doesn’t need to be registered.

10

Great!

So do I overwrite the information already in /etc/hosts

Thanks.

11

No you append to it.

12

OK. Great. I’ll do it.

13

I appended what you suggested to the hosts file. I also corrected the app.conf file where I placed what you suggested in the ServerName area and ServerAlias area.

I then tried getting my browser to display the context by trying all of the variations again and nothing works.

Any more suggestions?

Thanks in advance.

14

Send me the full Apache configuration file and the full hosts file.
In the meantime you can try using a different browser or the same one in guest mode.

15

Whenever I try to send this I get an error message from this site:

An error occurred: Sorry, new users can only put 2 links in a post.

16

OK. It looks like it may have gone through.

17

No. I got this email back:

We’re sorry, but your email message to [“incoming+770543b20c47e6b2e2124def7308d1f0@almalinux.discoursemail.com”] (titled Re: [AlmaLinux] [Support] Trouble with HTTPD Continued) didn’t work.

Reason:

Sorry, new users can only put 2 links in a post.

If you can correct the problem, please try again.

18

If you want to reach me where I can send you these:

elpeeps56
at

Thanks!

I got fastapi up and running in Nginx on Debian 10 exactly the way it should run in AlmaLinux on httpd.

smitsky

19

You can contact me on LinkedIn if you want here:

https://www.linkedin.com/in/noam-alum

But I seriously think this project might be a bit over your head at the moment.
I can fix the issue for you but It would be better for you to learn the fundamentals of how the Internet works in regards of Apache or any other web-server of sort before jumping to port forwarding.

I have a little guide I made on the basics of how web-servers work here:

Noam Alums - Web hosting

20

Thanks. Yes. I want to learn. I’ll take a look at your guide.

I appreciate the help.