Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

NoTimeForCaution's avatar

FORGE AND AWS FAIL

After failing to deploy via AWS Elastic Beanstalk - I've decided to let Forge do the provisioning.

So, IAM user created (EC2/VPC Unlimited Access) and connection successfully created in Forge.

Forge will create the EC2 Instance and then the server disappears on the Forge dashboard. I'm using the default VPC setting which allows all inbound/outbound traffic. Forge knowledge base says this is happening after failure of Forge to SSH the server.

Any ideas? Been a rough day.

0 likes
4 replies
Cronix's avatar

Contact Forge support. Log into forge (or just go to the login page) and click the big blue circle icon in the lower right. Just hit "enter" in the search part then click the "send a message" link to fill out the support form. They hide it pretty well for some reason.

NoTimeForCaution's avatar

Thanks @cronix

I just provisioned a new server and allowed Forge to create the VPC so I could inspect the settings. Their custom created VPC Inbound rules shows all Traffic but also includes TCP and UDP types.

I'm going to duplicate on my default VPC and see what occurs. I'll reach out to Forge for help as well. Thanks, man!

NoTimeForCaution's avatar

So the result is the same as when I deploy without Forge. Laravel and Tailwind components are shown but none of my Vue components are rendered.

Here is my package.json

{
    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development -- --watch",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
        "prod": "npm run production",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    },
    "devDependencies": {
        "axios": "^0.18",
        "cross-env": "^5.1",
        "laravel-mix": "^3.0.0",
        "laravel-mix-tailwind": "^0.1.0",
        "lodash": "^4.17.5",
        "tailwindcss": "^0.7.2",
        "vue": "^2.5.17"
    },
    "dependencies": {
        "@fortawesome/fontawesome-svg-core": "^1.2.8",
        "@fortawesome/free-brands-svg-icons": "^5.5.0",
        "@fortawesome/free-regular-svg-icons": "^5.5.0",
        "@fortawesome/free-solid-svg-icons": "^5.5.0",
        "@fortawesome/vue-fontawesome": "^0.1.2",
        "vue-js-modal": "^1.3.27"
    }
}

I'm assuming that the dependencies aren't being loaded but Tailwind is working and is only listed as a devDependency.

Could this be the issue?

NoTimeForCaution's avatar

Turns out the issue stemmed from HTTPS configuration in Laravel app.

Please or to participate in this conversation.