Well lets address one, then the rest is probably needs the same alteration.
Which web server are you using, Apache or Nginx?
Well lets address one, then the rest is probably needs the same alteration.
Which web server are you using, Apache or Nginx?
Apache, Why would it change because the OS 169 to 170 on a system that is not part of IPFire?
Because they started using name correlation in Apache.
For example.com
the configuration file should be: example.com.conf in /etc/apache2/sites-available for each web site on that server.
and the entry for each website config file should look like:
<VirtualHost *:80>
ServerAdmin admin@example.com
ServerName example.com.
ServerAlias www.example.com.
DocumentRoot /var/www/example.com./public_html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
So, Looking a my setup for the pages, Noting looks wrong. Mail Server, SFTP sites, Web Pages, VPN, all fail by one OS update on IPFire. I did as I said about a lot of times. Put in a Firewall ROUTEROS works fine. Test 193 does not work. I am planning coming in on the weekend to work on it again. Yet nothing to help point to the problem. or a FIX.
Unless you are trying to use a different DNS on the server or you donāt have TCP port 80 and 443 rule forwarded, I really donāt see why its not working. But the IPFireās DNS has to be the resolver since you donāt have a dns installed on the web servers themselves.
I donāt think routeros has a dns server.
I do not have a fixed IP so can be of little help.
But what do you fire wall rules look like?
source = any
NAT = firewall (ip you need)
destination = host
or
destination = IP
A thought came to mind:
if the cause of the problems has to do with Reverse Path Filtering?
edit
I found my old posts on this topic but the author of the topic did not reply.
Regards
I would like to share some additional details that may help clarify what has been discussed so far. To dive deeper, here are two previous posts that help explain the point of view Iām trying to express:
This is how I had understood the problem, and @dean8 confirmed that my interpretation was correct. Still, it seems odd to me that the servers are reachable via IP but not via FQDN. Iām wondering what could explain this inconsistency, since with 169 it works.
OK, it is done. 193 works but still have no idea why. 191 did not work, Clean build of a system. Hand keyed the first website. Tested it came up. The second came up. The first time in a long time the webpages are working. I did a restore from a backup. Everything works still. Turn off the wifi on my phone to double check everything still works. I have 6 computers just for this now. Setup a backup system and restored it from a backup and it works.
I started this weekend thinking still it would fail. No one had an answer after a year of trying to get this to work.
What was different. IPs change from the ISP, I named Hosts for the local servers. Alias no changes. I did not name Hosts for the Public IPs.
Still do not know why it started working. Just happy it did.