Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: Unable to Deploy Appsmith on Heroku - Error: caddy process exited with error: exit status 1 #33555

Closed
1 task done
ame-appsmith opened this issue May 17, 2024 · 0 comments · Fixed by #33559
Closed
1 task done

[Bug]: Unable to Deploy Appsmith on Heroku - Error: caddy process exited with error: exit status 1 #33555

ame-appsmith opened this issue May 17, 2024 · 0 comments · Fixed by #33559
Assignees
@Nikhil-Nandagopal @pranavkanade
Labels
Bug Something isn't working DevOps Pod Issues related to devops Heroku Issues related to Heroku High This issue blocks a user from building or impacts a lot of users Needs Triaging Needs attention from maintainers to triage Production

Comments

@ame-appsmith
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Description

The user is experiencing an error when deploying Appsmith v1.25 on Heroku due to port permission denial. This is the error message received in the logs:

2024-05-17T08:45:00.327915+00:00 app[web.1]: Error: caddy process exited with error: exit status 1```
The issue revolves around a permission denied error when trying to use port 80. Despite attempts to set the PORT variable and install the application from Heroku Elements, the problem persists.

More details and full logs are in [this ticket](https://internal.appsmith.com/app/oracle/ticket-details-662d74ffc3e4d34941e56ede?zid=2010).

### Steps To Reproduce

1) Installed the Appsmith application from Heroku Elements: [Appsmith on Heroku](https://elements.heroku.com/buttons/appsmithorg/appsmith)
2) Attempted to set the PORT variable on Heroku, but the issue persists.
 The user does not have access to the Profile or other configuration files to make manual changes.

### Public Sample App

_No response_

### Environment

Production

### Severity

High (Blocker to building or releasing)

### Issue video log

_No response_

### Version

v1.25
@ame-appsmith ame-appsmith added Bug Something isn't working Needs Triaging Needs attention from maintainers to triage Heroku Issues related to Heroku labels May 17, 2024
@Nikhil-Nandagopal Nikhil-Nandagopal added High This issue blocks a user from building or impacts a lot of users Production labels May 17, 2024
@github-actions github-actions bot added the DevOps Pod Issues related to devops label May 17, 2024
@AdeshAtole AdeshAtole mentioned this issue May 19, 2024
Merged
2 tasks
sharat87 pushed a commit that referenced this issue May 21, 2024
@AdeshAtole
fix: Consider heroku deployment while generating Caddyfile (#33559)
5ad365a 
## Description

Looks like while replacing NGINX with Caddy, Heroku deployment usecase
was missed.
Updated Caddyfile generation to use `$PORT` if available.

Fixes #33555 

Tested on Heroku Standard-2x Dyno.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Nikhil-Nandagopal Nikhil-Nandagopal

@pranavkanade pranavkanade

Labels
Bug Something isn't working DevOps Pod Issues related to devops Heroku Issues related to Heroku High This issue blocks a user from building or impacts a lot of users Needs Triaging Needs attention from maintainers to triage Production
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Consider heroku deployment while generating Caddyfile AdeshAtole/appsmith
3 participants
@Nikhil-Nandagopal @pranavkanade @ame-appsmith