No web inside www container [Solved]
Hi,
I'm running Daedalus, last version.
I click on the locked www icon, Chromium opens, but cannot reach any website.
The computer is using a wired connection.
What should I try to solve this?
Discussion, talk and tips
https://forum.puppylinux.com/
Hi,
I'm running Daedalus, last version.
I click on the locked www icon, Chromium opens, but cannot reach any website.
The computer is using a wired connection.
What should I try to solve this?
same here on locked www only
I have the same problem, just checked, and it is with both containerized browser and containerized daedalus. And I am using version 6.5
No problem for me
Daedalus and ScarthGap 6.5.5.1
Chromium works as always.
pp4mnklinux wrote: Fri Dec 20, 2024 1:18 pmNo problem for me
Daedalus and ScarthGap 6.5.5.1
Chromium works as always.
Did you click the online link?
@pp4mnklinux
did you click the addy?
I dont have problem on Scarthgaph`s locked www, only in Daedalus.
CF-DKS wrote: Fri Dec 20, 2024 1:52 pmpp4mnklinux wrote: Fri Dec 20, 2024 1:18 pmNo problem for me
Daedalus and ScarthGap 6.5.5.1
Chromium works as always.
Did you click the online link?
What link?
Please , give me a capture or photo of what u are talking about.
Thanks
Thanks
pp4mnklinux wrote: Fri Dec 20, 2024 1:18 pmWhat link?
Please , give me a capture or photo of what u are talking about.
Thanks
The screenshot you posted is local, not on line. Click the online link or try to access an online site.
Ok.- tested now
As @bugnaw333 said, no problem with ScarthGap, only with Daedalus.
@BarryK
OK, I'll look into it, probably tonight.
Observations :
- The problem is not limited to the www container, it exists for all the containers in Daedalus( tested with daedalus as container and the terminal container (test with ping) )
-In the www container google.com (as well as the chrome web store and youtube) works.
- By typing chrome://net-internals/#dns in the address bar of chromium and using the Lookup button you can get the ip adress for a site:
For example, the ip adress of forum.puppylinux.com is 162.241.244.127 (It's an IPv4 adress)
The ip adress of google.com is 2a004007:807::200e . It's an IPv6 adress.
-
Code: Select all
Ping 2a00:1450:4007:807::200e
in the terminal container works
- There is no line starting by inet in the outputs of the commands ip addr show and ifconfig in the terminal container, but there are lines starting by inet6
So in the containers in Daedalus, IPv4 do not work but IPv6 works
EDIT : command nmcli in the terminal container (in Easy Daedalus 6.5.1.1)
# nmcli
Erreur : impossible de créer l'objet NMClient : Impossible de se connecter : No such file or directory.
(In English : Could not create NMclient object. No such file or directory)
I tracked down the cause.
In script /usr/local/easy_containers/ec-chroot, line 486, this line:
Code: Select all
ip netns exec ${IFcont}ns dhcpcd -C resolv.conf -C wpa_supplicant -b ${IFcont} #-b background immediately. 181117 do not write to /etc/resolv.conf
fails, because 'dhcpcd' executable is missing.
networkmanager uses its own inbuilt dhcpcd, but for ethernet connection in container, require the dhcpcd executable. The script sets up an "ethernet bridge" into the container. I did that code back in 2018, and memory of how and why is very vague.
Anyway, you have to use PKGget to install 'dhcpcd-base' package. That fixes it.