It was fine when I first started it, but now after turning my pi on the next day, it doesn't work. I might have changed something I shouldn't have, so I can run owncloud as well. But it looks like I can't, because both want port 80, and I've yet to find a way to swap one of them
You shouldnt change Pi-hole's lighttpd port 80 TCP, or else Pi-hole wont be able to return a block page instead of an ad.
And if you cant change the port for Owncloud, adding a secondary IP address to the system could offer a solution if you bind the daemons to their particular IP addresses.
Some pointers in below posting on how to bind Pi-hole's dnsmasq and lighttpd daemons:
You can create a working software fake eth1 with it's own ip.
Configure lightpd to use only the real ip on eth0
Configure owncloud to use only eth1 (the fake)
Or the easy way: tell owncloud to use a diffrent port.
What do you mean ? A dummy interface ?
That will only complicate matters as you'll need additional bridging to let the dummy talk over the physical interface.
No, you can create a "real" eth1 that is based on eth0.
Do not have the command available right here, but my pihole is working with this trick.
As soon as I can reach my console I can send you that command.
ip link add link eth0 address 00:11:11:11:11:11 eth6 type macvlan
ifconfig eth6 172.16.25.125 (or whatever)
ifconfig eth6 netmask 255.255.255.224 (or whatever
ifconfig eth6 up
Nice and clear Johan!
I never needed and bridging with ip link add macvlan in pihole and I am also running 2 http servers on port 80 (pihole and nxfilter) on 1 raspberry.
Hope anchovey707 can now run his 2 http servers....
however ....owncloud on a rasberry. Seems performance is not an issue for anchovey707
Unix is not my daily os...can't offer any more tricks in this case.