microLXC Public Test

World

Looks this time it will work.

e5a8-b9b9-a75a-de9f

Neoon

@World said:
UPDATE: After got this error, tried to re-login and submit the deploy request again, sometimes it will get the same error, but sometimes it will return 'Cooldown, wait for a bit.' .
As only applies Cooldown if do a successful deploy, it seems strange.

Now I've deleted account, will wait for some time then try to deploy again.

Well, if the request gets rejected, the request will stay in the database.
Until the cronjob will delete it, which is in a few minutes.

To be fair, its technically a delay but a small one.
I updated the backend, to clean up the request on delivery.

Means if you click on Try again, you can instantly try again without any delay anymore.

Thanks for the information, I've tried three times in the last hour, but all returned this error, will try again later then.

For some reason, LET did not issue a token in the first place.
I added a cronjob which takes care of refreshing it, but as I said, it will only reduce the error rate, not fully remove the issue.

World

@Neoon said:

@World said:
UPDATE: After got this error, tried to re-login and submit the deploy request again, sometimes it will get the same error, but sometimes it will return 'Cooldown, wait for a bit.' .
As only applies Cooldown if do a successful deploy, it seems strange.

Now I've deleted account, will wait for some time then try to deploy again.

Well, if the request gets rejected, the request will stay in the database.
Until the cronjob will delete it, which is in a few minutes.

To be fair, its technically a delay but a small one.
I updated the backend, to clean up the request on delivery.

Means if you click on Try again, you can instantly try again without any delay anymore.

Thanks for the information, I've tried three times in the last hour, but all returned this error, will try again later then.

For some reason, LET did not issue a token in the first place.
I added a cronjob which takes care of refreshing it, but as I said, it will only reduce the error rate, not fully remove the issue.

Thanks a lot, it has been deployed successfully

Shot2

3918-be06-69f5-0a9a

Back on track...

NanoG6

c4c8-c866-1285-3df9

NanoG6

c4c8-c866-1285-3df9

Neoon

Singapore IPv6 has been fixed, enjoy.

Timtimo13

84f8-1bdb-f057-b927

NanoG6

Is there any chance to get more storage (SG)?

Neoon

@NanoG6 said:
Is there any chance to get more storage (SG)?

What do you need?
You could upgrade from micro to tiny.

NanoG6

Already on tiny, currently 1.6GB left. Need about 2-3GB more to move my blog there.

Neoon

@NanoG6 said:
Already on tiny, currently 1.6GB left. Need about 2-3GB more to move my blog there.

Its not planned and there is not such a thing to upgrade a individual container yet.
But, I thought about upgrading the packages.

Means micro gets 1.5GB instead of 1.3GB, tiny gets 3GB instead of 2.5GB.
Additional, a 384MB Package, with 4GB but only available in Australia, Netherlands and Norway.

You could snag a storage one, if it gets available at some point.

Neoon

In about 2 weeks, the system will check for certain activity on the containers.
Means for you, you should have logged into the panel or container before this update is released.

After this update, you have to login every 60 days, either ssh into the container or login into the panel.
If you fail to meet these requirements, your container goes into a 7 day grace period, afterwards it will be stopped, 7 more days and your container will be deleted.

The reason why I did choose a login based activity is, depending on your use case you may have low traffic,memory or cpu needs, so we cannot really pin it down by that.

We will see how this works and it might be changed later but for now it should be fine.

Levi

What is the goal of this project? Final stage. Is it going to be monetized?

Shot2

Steal our precious fluids

Neoon

@LTniger said:
What is the goal of this project? Final stage. Is it going to be monetized?

I was interested and still are, to play around with LXD (LXC), thus creatus est microLXC.
The about page brings it quite to the point.

monetized? could be.

@Shot2 said:
Steal our precious fluids

elwebmaster

Thanks, very smooth activation!

lontong

ae17-29c0-311c-27a5

Neoon

NL is currently asleep, working on resolving it.

edit: Maintenance, Node is back online.

kennsann

4dba-3b10-3c8d-3a84

Neoon

@kennsann said:
4dba-3b10-3c8d-3a84

Sorry for the late response.
The images are now preloaded on all nodes, please try again.

Edmond

Any chance that Singapore might be restocked soon? Thanks for doing this!

shyaminayesh

can I have one. I only have 47 posts 😓

Neoon

@Edmond said:
Any chance that Singapore might be restocked soon? Thanks for doing this!

SG has been upgraded, I do a reboot tomorrow, more stock will be available by then.

@shyaminayesh said:
can I have one. I only have 47 posts 😓

These are the minimum requirements so no.

smile93

a299-9280-ebd8-b9de

zenki

5525-35aa-88a3-e6eb

kennsann

0736-32fe-801b-3977

Edmond

034e-cd95-5801-d7e2

Edmond

@Edmond said:
034e-cd95-5801-d7e2

@Neoon It's taking quite a bit of time to try and deploy a VPS... is it stuck by any chance? It seems I can log into the account that was created with another browser tab but there's nothing set up and it's forever stuck at the deployment stage...

If this is normal, please ignore this!

Neoon

@Edmond said:

@Edmond said:
034e-cd95-5801-d7e2

@Neoon It's taking quite a bit of time to try and deploy a VPS... is it stuck by any chance? It seems I can log into the account that was created with another browser tab but there's nothing set up and it's forever stuck at the deployment stage...

If this is normal, please ignore this!

Nah, its not normal.
I did a reset on the job and it ran through.

So you can login and start using it.