Hi.
Given that the list appears to be slow today, I'm posting an offtopic issue.
I can create a test website, running centos/apache: http://1.2.3.4/cat.php
i'm trying to get to http://test.com/cat.php
where I use something like cloudflare to implement the domain/url/DNS process.
Anyone have any pointers/docs that have step-by-step actions to do this.
.. instead of http://1.2.3.4/cat.php i'm trying for http://test.com/cat.php
thanks
On Mon, 2020-03-23 at 13:20 -0400, bruce wrote:
Given that the list appears to be slow today, I'm posting an offtopic issue.
I can create a test website, running centos/apache: http://1.2.3.4/cat.php
i'm trying to get to http://test.com/cat.php
where I use something like cloudflare to implement the domain/url/DNS process.
Anyone have any pointers/docs that have step-by-step actions to do this.
.. instead of http://1.2.3.4/cat.php i'm trying for http://test.com/cat.php
I presume you're using that as a faked domain name just for this email, since it already exists.
a. Your webserver needs to be configured to respond to your specific hostname, if it uses virtual hostnames to determine which site to respond to queries with. If it replies to all queries with the same site, this doesn't matter.
b. Your DNS server needs to have your domain name pointed at the public IP of the webserver.
You can do a test run of this on your own computer running Apache, just put your test domain name into your hosts file, associating it with your LAN IP address.
e.g. $ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.1 www.example.com example.com
NB: 192.168.1.1 is *my* LAN IP for one of my PCs, substitute your own. And the two example.com domain names are my faked examples.
Now, if your problem purtains to how to configure cloudfare, I don't know what to advise. Beyond that they should have help docs. If you're stuck part way through their help docs, send us the address for the help page you're looking at, and tell us where your stuck.
Hey Guys.
Thanks for the replies. I think I'm getting a bit of clarity.
Given that the list has/is sort of light regarding traffic, I'd like to post what I'm trying to do, and the complete steps I'm going to implement to get to my goal.
My initial goal is to have a Digitalocean VM, running centos8, that's running a live webapp (apache) that I'll be able to access via http://www.cat.com/a.php.
The base server will be having selinux/firewall/etc...
Given that I've never touched selinux, and only tangentially played with firewalls, I'm sure I'll screw things up.
If it's ok to post my steps, as well as my progress through the steps, I'd appreciate it. (Will help to know I have people I can turn to if I can't figure something out!)
Thoughts/Comments
thanks
-bruce
On Tue, Mar 24, 2020 at 7:23 AM Tim via users users@lists.fedoraproject.org wrote:
On Mon, 2020-03-23 at 13:20 -0400, bruce wrote:
Given that the list appears to be slow today, I'm posting an offtopic issue.
I can create a test website, running centos/apache: http://1.2.3.4/cat.php
i'm trying to get to http://test.com/cat.php
where I use something like cloudflare to implement the domain/url/DNS process.
Anyone have any pointers/docs that have step-by-step actions to do this.
.. instead of http://1.2.3.4/cat.php i'm trying for http://test.com/cat.php
I presume you're using that as a faked domain name just for this email, since it already exists.
a. Your webserver needs to be configured to respond to your specific hostname, if it uses virtual hostnames to determine which site to respond to queries with. If it replies to all queries with the same site, this doesn't matter.
b. Your DNS server needs to have your domain name pointed at the public IP of the webserver.
You can do a test run of this on your own computer running Apache, just put your test domain name into your hosts file, associating it with your LAN IP address.
e.g. $ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.1 www.example.com example.com
NB: 192.168.1.1 is *my* LAN IP for one of my PCs, substitute your own. And the two example.com domain names are my faked examples.
Now, if your problem purtains to how to configure cloudfare, I don't know what to advise. Beyond that they should have help docs. If you're stuck part way through their help docs, send us the address for the help page you're looking at, and tell us where your stuck.
--
uname -rsvp Linux 3.10.0-1062.18.1.el7.x86_64 #1 SMP Tue Mar 17 23:49:17 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On Tue, 2020-03-24 at 14:39 -0400, bruce wrote:
My initial goal is to have a Digitalocean VM, running centos8, that's running a live webapp (apache) that I'll be able to access via http://www.cat.com/a.php.
Again, that domain is already in use. If you want to use an unregistered domain on your LAN, pick something with a .lan suffix (or another suffix that is not used on the internet).
If you want to use a domain name on the internet, you need to register one. There are a lot of good reasons to own your own domain name (such as freeing yourself from being held captive by your ISP, by having your own email address that you can host anywhere), so if you can think of a good one, register it.
The base server will be having selinux/firewall/etc...
Given that I've never touched selinux, and only tangentially played with firewalls, I'm sure I'll screw things up.
I run Apache on CentOS and Fedora, though not as a webapp.
SELinux isn't a thorn in my side, though I don't know if webapps make that difficult. And I don't do any of those database website things (wikis, blogs, etc). They can be a SELinux headache (probably because they do things in wierd ways, some of them *do* want to run in a risky manner).
Firewalling isn't hard, either. The firewall configurator has a couple of tick boxes for HTTP and HTTPS.
-
bruce -
Tim