microLXC Public Test

jcn50 · January 6

Node in Chile/Valdivia seems down.

Neoon · January 6

@jcn50 said:
Node in Chile/Valdivia seems down.

No.
https://hetrixtools.com/report/uptime/cd63097c4a778e69284fdde2f376c3e7/

If you want support, you have to explain what is wrong, otherwise I can't help you.

Neoon · January 7

Maintenance announcement

On January 31st, Oradea will be offline for maintenance, approx. up to 12 hours.
Various upgrades will be carried out.

kadidala · January 8

a942-8b29-3cfb-9e76

thanks

TheOnlyDK · January 9

Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

Neoon · January 10

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

TheOnlyDK · January 10

@Neoon said:

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

It’s the original Tokyo. Not Tokyo Equinix

Neoon · January 10

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

It’s the original Tokyo. Not Tokyo Equinix

Its not the port forwarding its your VPS.

TheOnlyDK · January 10

@Neoon said:

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

It’s the original Tokyo. Not Tokyo Equinix

Its not the port forwarding its your VPS.

Hmm ok I think I may know why. Some of the templates don’t have ssh pre-installed. I bet that’s why. I thought I installed it before, maybe I didn’t. This is a downside with an ISP with no ipv6 connection.

Neoon · January 10

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

It’s the original Tokyo. Not Tokyo Equinix

Its not the port forwarding its your VPS.

Hmm ok I think I may know why. Some of the templates don’t have ssh pre-installed. I bet that’s why. I thought I installed it before, maybe I didn’t. This is a downside with an ISP with no ipv6 connection.

SSH is never preinstalled, its installed during deployment, I may fail.
Ideally we have premade templates with ssh installed, but currently I don't.

goxofy · January 11

It's such a shame, I'm not satisfied.

Neoon · January 11

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

It’s the original Tokyo. Not Tokyo Equinix

Its not the port forwarding its your VPS.

Hmm ok I think I may know why. Some of the templates don’t have ssh pre-installed. I bet that’s why. I thought I installed it before, maybe I didn’t. This is a downside with an ISP with no ipv6 connection.

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

TheOnlyDK · January 11

@Neoon said:

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:

@Neoon said:

@TheOnlyDK said:
Tokyo's NAT forwarding might not be working properly, can ping the IP but can't SSH via v4.

To help you I need more info.
We have 2 Tokyo nodes.

It’s the original Tokyo. Not Tokyo Equinix

Its not the port forwarding its your VPS.

Hmm ok I think I may know why. Some of the templates don’t have ssh pre-installed. I bet that’s why. I thought I installed it before, maybe I didn’t. This is a downside with an ISP with no ipv6 connection.

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

Appreciated!

brauni · January 11

e0b1-e8d2-6148-2689

igctt · January 12

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

vm created in Meppel still can't ssh login, and earlier I tried Helsinki it's also the same result.
Ah maybe Meppel and Helsinki are all in the 4 nodes?

Neoon · January 12

@igctt said:

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

vm created in Meppel still can't ssh login, and earlier I tried Helsinki it's also the same result.
Ah maybe Meppel and Helsinki are all in the 4 nodes?

I just tested it, works for me.
What template did you use?

igctt · January 12

@Neoon said:

@igctt said:

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

vm created in Meppel still can't ssh login, and earlier I tried Helsinki it's also the same result.
Ah maybe Meppel and Helsinki are all in the 4 nodes?

I just tested it, works for me.
What template did you use?

In Helsinki I tried alpine 3.22 and Debian 11, in Meppel I'm using Alpine 3.22

igctt · January 12

@igctt said:

@Neoon said:

@igctt said:

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

vm created in Meppel still can't ssh login, and earlier I tried Helsinki it's also the same result.
Ah maybe Meppel and Helsinki are all in the 4 nodes?

I just tested it, works for me.
What template did you use?

In Helsinki I tried alpine 3.22 and Debian 11, in Meppel I'm using Alpine 3.22

the host is lxcb6ef8a16 in Meppel

jcn50 · January 12

@Neoon said:

@jcn50 said:
Node in Chile/Valdivia seems down.

No.
https://hetrixtools.com/report/uptime/cd63097c4a778e69284fdde2f376c3e7/

If you want support, you have to explain what is wrong, otherwise I can't help you.

For both:

Chile/Valdivia [lxc5d17a63d]
Pakistan/Islamabad [lxcd4042927]

when I click on the "Manage" button I am getting the following error message:
Failed to contact Node, please try again later.
I cannot do anything from my side, since I can't even connect by SSH either (thus I assumed both servers were down).

I can see that PK is down on Hetrix, but not CL (as you showed me). So maybe it is linked with this:

@Neoon said: The cronjob was stuck, Validvia had a dsync, I cleaned up but I forgot one thing, hence it was stuck, fixed now.

Neoon · January 12

@jcn50 said:

@Neoon said:

@jcn50 said:
Node in Chile/Valdivia seems down.

No.
https://hetrixtools.com/report/uptime/cd63097c4a778e69284fdde2f376c3e7/

If you want support, you have to explain what is wrong, otherwise I can't help you.

For both:

Chile/Valdivia [lxc5d17a63d]

Pakistan/Islamabad [lxcd4042927]

when I click on the "Manage" button I am getting the following error message:
Failed to contact Node, please try again later.
I cannot do anything from my side, since I can't even connect by SSH either (thus I assumed both servers were down).

I checked, fine too, might be related to your container.
Send me a DM.

I can see that PK is down on Hetrix, but not CL

Already said, a Ticket is open, that's all I can do.

Neoon · January 12

@igctt said:

@Neoon said:

@igctt said:

Should be fixed now, except for the 4 nodes still running LXD and not Incus.

vm created in Meppel still can't ssh login, and earlier I tried Helsinki it's also the same result.
Ah maybe Meppel and Helsinki are all in the 4 nodes?

I just tested it, works for me.
What template did you use?

In Helsinki I tried alpine 3.22 and Debian 11, in Meppel I'm using Alpine 3.22

Debian works, but Alpine seems to be broken.
You fix one thing another one breaks, neat.

igctt · January 12

Debian works, but Alpine seems to be broken.
You fix one thing another one breaks, neat.

Only Debian 13 works, ssh config is wrong in Debian 12, don't accept public key ssh login, will ask a password while pub key is set; Debian 11 is not working, and also almalinux 9

Neoon · January 13

@igctt said:

Debian works, but Alpine seems to be broken.
You fix one thing another one breaks, neat.

Only Debian 13 works, ssh config is wrong in Debian 12, don't accept public key ssh login, will ask a password while pub key is set; Debian 11 is not working, and also almalinux 9

Debian 11, 12 and 13 works fine, stop bullshit me please.

If its seriously not working, lemme know.
I check on Alpine and Almalinux later.

igctt · January 13

Debian 11, 12 and 13 works fine, stop bullshit me please.

If its seriously not working, lemme know.
I check on Alpine and Almalinux later.

Thank your for your supporting community.
I'm not talking nonsense, after reinstalling Alpine 3.22 I installed Debian 11 and 12, they're all can't ssh login. It seems some files will not be changed during resinstall, in another vm I found once that the sshd_config is still the old one after reinstalling.
anyway, it's not an emergency. take your time.

Neoon · January 15

@igctt said:

Debian 11, 12 and 13 works fine, stop bullshit me please.

If its seriously not working, lemme know.
I check on Alpine and Almalinux later.

Thank your for your supporting community.
I'm not talking nonsense, after reinstalling Alpine 3.22 I installed Debian 11 and 12, they're all can't ssh login. It seems some files will not be changed during resinstall, in another vm I found once that the sshd_config is still the old one after reinstalling.
anyway, it's not an emergency. take your time.

After you said, Debian 11, 12 and 13 is broken, I did a deploy of each it worked fine.
The rest has been fixed too, except Archlinux.

If something is broken, explain what is broken, otherwise I am not gonna offer support.

Neoon · January 16

PK is back online, I am sorry for the downtime, but it took 14 days+ for a ticket response.

Neoon · January 17

NZ connectivity issues on IPv4 should be solved too.
Ticket took a bit to find the cause.

jcn50 · January 17

@Neoon SSH port to my container [lxcd4042927] in PK/Islamabad does not work. I have re-installed the OS from the Dashboard but it doesn't change anything. The netstat -tulpn command is showing me that the SSH service is running properly on port 22, and also the other service that I am running on another port, unfortunately I cannot connect to any of them.

bbass · January 17

Hi, lxc164802f9 - Valdivia, i can't ssh, i've tried ipv4 ipv6 from different ip's, restart/stop the server, reconfigure the network and reinstalled Alpine 3.22 ... none of them worked from my end, can you have a look please, thanks

Neoon · January 17

@jcn50 said:
@Neoon SSH port to my container [lxcd4042927] in PK/Islamabad does not work. I have re-installed the OS from the Dashboard but it doesn't change anything. The netstat -tulpn command is showing me that the SSH service is running properly on port 22, and also the other service that I am running on another port, unfortunately I cannot connect to any of them.

Yea the port forwarding was broken due to their maintenance.
Fixed now.

@bbass said:
Hi, lxc164802f9 - Valdivia, i can't ssh, i've tried ipv4 ipv6 from different ip's, restart/stop the server, reconfigure the network and reinstalled Alpine 3.22 ... none of them worked from my end, can you have a look please, thanks

Did you check if SSH is running? Basic troubleshooting steps.

Howdy, Stranger!

Categories

In this Discussion

microLXC Public Test

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

microLXC Public Test

Comments