I installed Project eBlocker over the weekend and had some problems accessing everywhere,
like with my PiHole system which is lying in the corner at the moment.
A large part of the difficulties I got under control.
FritzBos - DHCP OFF, eBlocker switched to indivituelle DNS settings.
My problem is now on a NAS with e.g. http://IP-NAS:5055/ I get no access,
the http://Subdomain/admin/ I get access.
What settings must be made in eBlcker to make it work?
@hirsk Sorry, I have no idea where you are at. Please share the info asked in the README and describe in detail what you have done - and trying to achieve.
I.e. I‘m already confused by the headline as there is VM - but no docker support 🤔
And yes, of course the VM get‘s a separate IP (from a DHCP server) next to the existing host‘s IP. To address eBlocker in the VM you need to use the VM‘s IP - but not the IP (or domain name) of the host. But maybe that‘s not the question?
THX!
@hirsk
Hi,
my network is set up also with eBlocker Individual Settings.
In my network, there is running a PI with Docker and serveral other servers, with services like
NFS and SMB, Webserver.
There I have no problem.
When you want to access yput NAS with internal IP on port 5055 it is not running over the eBlocker.
But one hint, on eBlocker I set for some servers the domain name to the internal ip. So the traffic is only in the internal network.
Example: docker.mydomain.de --> 192.168.178.20 (under local device names (lokale Gerätenamen))
in the www there is docker.mydomain.de --> the external IP of my internetrouter
Hope ths helps
Regards
PIO78
Before I tried to integrate ioBroker into the home network everything worked!
I changed the NAS from manual setting to DHCP and in one fell swoop it works again.
3 days my head was on fire!!!
Sorry for my first positive feedback on this topic, I had reset the network from the NAS and replied right away.
After I changed the setting on the NAS and switch back to Link Aggregation, it does not work again.
So this is the key to the problem the eBlocker does not cope with this.
@hirsk Unfortunately I‘m lost in translation and/or the info you‘ve share is to sparse to help.
From what I understood: You try to run eBlocker VM-Edition on a NAS. Right? Which NAS? Which VM image?
I also don‘t understand your NAS network changes at all. There is no need to change any (network) settings on the NAS when eBlocker runs in the VM. So I fear that‘s the source of all errors. All network configuration is done via the eBlocker interface only. And as I said above: your NAS will have two different IPs (one for eBlocker, one for NAS) when running the VM-Edition. This avoids a conflict of URLs…
Sorry, based on the sparse info given I‘m unable to help more. Again, please share the info asked for in the README to stop guessing and get quick help.
THX!
@hirsk Even we have not heard back from you, I‘m marking the topic solved. I assume eBlocker generally works for you now as you‘ve started asking other forum question indicating this… 😉
Don‘t hesitate to add to this thread in case you need further help 👍
THX!