Installing custom VPS wont work

@robinvm How about giving us adequate context to answer your question. Right now, it is so vague that you are not going to get any real help.

As soon as the command forge provides is done the server goes on provisioning and keeps stuck on that, i dont have more info then that srry

Sounds like your account permissions or a key is incorrect. What service? If it's AWS then search here for answers because I know the account IAM needs to be setup a certain way.

If it's a custom VPS do check your firewall is allowing the server is able to contact forge on port 80 (HTTP) and 443 (HTTPS).

When the script runs Forge will show "provisioning" until the script completes and does the callback (with sudo password and other key stuff) on script completion.

(I only know this as I'm setting up a custom VPS today and it got stuck... guess who didn't open the firewall!)

Hi gang. I'm having this same issue. It's a fresh install of Ubuntu 16.04. All ports are open (no firewall configured). I even set server up as my network's DMZ to make sure my network isn't blocking any ports.

I am logged in as root, not doing this via sudo.

The forge.sh script runs for a good 6 or 7 minutes doing it's thing. There's nothing that jumps out at me during the script that looks out of place. No critical error messages I can see.

Unfortunately there is no feedback from the script that indicates if it was successful or not. If there's a log file that's generated somewhere I can't find it.

I took a look at the script and I've tried running the curl post at the end manually but even when it returns a 200 response code there is no change, the Forge servers list still shows the server as provisioning.

I verified that all the services (I'm pretty sure all) that the forge.sh script installs are in fact up and running (as root service --status-all).

Finally I manually updated the nginx catch-all config to return a static HTML page and that works fine from outside the network where my Ubuntu server is installed.

So, does anyone know what, if anything, is supposed to return from the forge callback at the end of the forge.sh script?

Is there a log file that is generated during the script execution I can use to debug?

I'm happy to provide additional info to help troubleshoot!

@dyoung@volume9inc.com i know how to fix this, you got a twitter or whatsapp or skype i can help you on?

Hey @robinvm and @dyoung@volume9inc.com what do you guys know that I don't? Having this exact issue.

@eclev91 What is your issue exactly?

@haykd So my server has been provisioned, the forge.sh script ran successfully, and when we run the final call back home in forge.sh, we can see a subsequent SSH connection attempt from Forge. It logs in, and then disconnects, and in the Forge dashboard, it continues to spin "Provisioning". Oddly enough, the "Connection" column in the dashboard shows "Successful" when I refresh it. So despite being able to successfully connect via SSH, Forge doesn't "finish" provisioning my box.

I reached out to Forge support and tried to get details on what exactly Forge is looking for or trying to do when it SSH's in so that I could try and debug, but they haven't offered any details and respond intermittently.

@eclev91 I see. I would request Forge support to review and fix the issue.

@haykd been there done that. Less than helpful, and have told me to simply use DO or AWS, which I normally do, but hands are tied by client requirements on this one.