New host generation is wrong (Singapore server only)

[fu-sen]

I'm trying to host a new Singapore server, but it spawns several times and it all fails.

When I look at the deploy, I see the following line.

CRITICAL: SSH login failed. Most procedure will not execute.

The generated website is returning ERR_TOO_MANY_REDIRECTS.

In line with this, the portal response is currently significantly worse. I sometimes see the 502 Bad Gateway.
I feel that something is obviously wrong.
Even in this state, the New York server successfully created a new host. Therefore, I am reporting to domcloud-id.

[willnode]

I forgot to turn the swapfile on. It should back to normal now.

[fu-sen]

Yes, the response is obviously faster. When I looked at the system status, swap was 0B.

I will try to work on the portal again.

[willnode]

Yeah, it's a common mistake. Now I have put this under cron job bootup so I won't need to turn it back on manually again.

[fu-sen]

No, it was too fast to close the issue. The portal response is lighter, but creating a new host is still problematic. There still seems to be some other problem.

[fu-sen]

The New York server can successfully generate a new host, but there is a problem with subsequent template generation.
The issue is related to dom-portal, but you are aware of it so let's continue with this issue.

[willnode]

I noticed that in some cases invoking webmin host creation took longer than 30 seconds, which is the maximum time NginX can process. I will try to put it as a background job instead.

[fu-sen]

I have confirmed that the New York server *.domcloud.io works perfectly, including the template behavior.
On the other hand, the Singapore server *.dom.my.id cannot be newly used even now because the host creation is abnormal.
Something is wrong with the Singapore server.

[willnode]

I checked your log files, it turns out the sga server actually correct. You missed the fastcgi: off and firewall: off hence the firewall kicks in. The firewall isn't gone, just need to be disabled explicitly.

You just need to put those to your existing template. No need to separate the template because the deployer knows the execution order automatically.

Btw, the nyc server had problem with it's iptables config. Turns out iptables config is far less reliable than nginx one. It gone back now.

[fu-sen]

I am trying 2 different steps at this time.

• Template containing root: public_html/site: This should turn off the firewall.
• Default template: I created a new host regardless of the template. The following contents

features: ['mysql', 'ssl']
nginx:
  ssl: on

So what I'm talking about right now is a problem that's occurring independently of the template.

[willnode]

No, just setting the root to a subfolder doesn't turn it off, neither fastcgi: off. Explicitly telling firewall: off will do.

And by default firewall record will be added after creation of new host,

[fu-sen]

Hmm? You seem to be looking only at the effects of firewalls. See the original text where I put this issue. I'm not talking about firewalls: #5 (comment)

[fu-sen]

I created a Singapore server with the default template. You will know the host name. Please understand what is happening again.

[willnode]

Ok I know the root problem. There's rogue username exist with that same name and that's prevent the creation of new host. Deleted it now.

[willnode]

Anyway, feel free to drop an email to me if you need to solve problems privately.

[fu-sen]

Oh awesome! Our DOM Cloud is back.

I revived the GitHub project during this time. I needed that template. I also added a setting to disable the firewall:

• https://github.com/fu-sen/DOMCloud-MkDocs
• https://github.com/fu-sen/zerossl.domcloud.io

https://mkdocs.dom.my.id/ wouldn't have been created by anyone other than me. It seems half-baked by creating or deleting.
Probably the timing when the load on the server was high.

It's time to close the issue. After that, we need to be careful about malicious attacks again.
Thank you for your support so far.

p.s. I'm looking at my profile, has PayPal payment been enabled?

[willnode]

Glad it worked now.

PayPal is enabled, though nobody has tested to pay with it so far.

[fu-sen]

PayPal is enabled, though nobody has tested to pay with it so far.

https://domcloud.io/price

FAQ What are the payment methods? Has not been updated.
I can work with PayPal, so I might be the first one. I am thinking about that possibility.