New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Comments
@Neoon 1002-1aaf-37a1-8acb
295a-5a89-5f44-0078
I have a node on the Tokyo Equinix node and my container does only have NAT ipv4 but i don't seem to see the ipv6 config
ping6 -c 3 google.comWorks ?
ping6: connect: Network is unreachableDashboard says "
IPv6 Not available"my LXC IP is 10.0.13.50 or my hostname is lxca23451dc if @Neoon could check?
I checked
/etc/network/interfaces(Does not exist, hence LXC)Running
systemctl status systemd-networkddoes work but i only see my LAN IPV4. I also checked "/etc/systemd/network/eth0.network" and i don't see anything related to ipv6 since this is a fresh Debian 13 install. the one on my Sandefjord mediumNOKVM LXC/vps works fine, i do have a dedicated random ipv6 thereIPv6 isn't available for Tokyo Equinix.
No, if the Panel says "IPv6 Not available" its not available.
The Location never had IPv6 available.
edit:
However you could ask @Abd if IPv6 is available there now.
2b3d-85c7-2961-9102
ef2c-538b-fdef-2aa4
My server won't boot up, and restarting it from the control panel doesn't help.
I tried booting from an ISO to retrieve the files, but that doesn't work either.
Please take a look and see what happened.
Helsinki 1e36-b248-3c94-f564
Its running and its booted.
Any error message?
There are no errors in the control panel
but I can't connect.
Shell and Console in the control panel aren't working either; just a black window.
try Spice and check what it gives you as output.
edit: I am gonna have another look
Black screen and "Websocket connection failed " in the Chrome console
Something broke, the backend is unhappy with the sessions, hence requests get blocked.
I will look into it.
Console / Spice isn't working due to a recent Incus update.
They added additional checks, in the LTS version, without really telling anyone.
Hi @Neoon ,
Just wondering, is the node Johannesburg down?
Thank you.
We have a status page, so there is no need to ask.
If you have a problem, don't be cryptic.
Yes, there is nothing worse than spending an hour struggling with keys.
Skill issue.
PK is back online since about 2 days.
I missed the email from hetrix, however I got a Ticket response yesterday.
Someone or something fixed PK, but I don't know who, the Support that replied yesterday denies any allegations.
Basically they just replied that the VM is working and Online, as far as I know last time I checked I couldn't even boot it.
Anyway, enjoy your PK containers everyone.
I am unsure at this point if I gonna enable deployments on PK again.
The Console is currently still broken, I dislike most "fixes", I don't have a propper non hacky solution yet.
The console issue has been fixed, sorry that it took so long.
The patch included security fixes, so I could not hesitate updating incus/lxd.
@Neoon
Thanks for your work!
The console is now working on my servers except 1e36-b248-3c94-f564
Shell: Connected Disconnected
Console: WebSocket connection failed
Spice: WebSocket connection failed
SSH to this server also doesn't work.
In which location is this LXC? (I'll try on my side too)
No Helsinki works.
Shell / Console does only work when your VM is booted up and has the agent installed.
Spice should work in any circumstance.
However, your websocket connection is bound to your sessionID, means you can only have one active at a time.
If you try to open more than one, it gets blocked, if your request isn't as expected, it gets blocked.
Try a different browser.
You can DM me your sessionID (check your cookies), so I can check the logs.
Hey! been told to check this out by some friends.
6e8f-4783-60db-7643
Thanks.
97a0-9847-ec27-b111
cbb0-264e-eeef-067f
dab9-ecaf-9e3d-ad55
Johannesburg is not working. I cant deploy a container on it. According to the status page it seems to be online but everytime i am trying to deploy a container, I always get "Deployment of the container failed,
please try again." @Neoon could you please check whats wrong ? Thanks