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.

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

Add configs and instructions for deploying to Heroku #9

Closed
wants to merge 5 commits into from
Closed

Add configs and instructions for deploying to Heroku #9

wants to merge 5 commits into from

Conversation

ianrandmckenzie
Copy link

@ianrandmckenzie ianrandmckenzie commented Dec 13, 2021

Hello again!

I wanted to make a separate service for Minecrafters, and in that process, I added some Heroku configs for myself. I thought I'd add the Heroku-specific work to your repository in case people may want to spin up a quick Heroku app on their own. A live Heroku example of this branch can be found here:

https://log4shell-heroku-example.herokuapp.com/

I plan on taking this app down once this PR is rejected/merged.

Cheers,

Ian

@kiyell
Copy link

kiyell commented Dec 28, 2021

@ianrandmckenzie

So I tried this configuration and followed the instructions and was able to spin up a Heroku app. However, although the web service appears to work, it doesn't look like the LDAP port is open. For example I tested this with curl:

curl "ldap://herokuinstance.herokuapp.com:1389" doesn't work
curl "ldap://log4shell.huntress.com:1389" works

Researching this further, it appears that Heroku doesn't allow you to open non http standard ports and use binary protocols like LDAP (https://stackoverflow.com/questions/6063731/ldap-server-on-heroku)

@ianrandmckenzie
Copy link
Author

@kiyell Thanks for catching that! It looks like you're right, re: Heroku not supporting the ldap protocol. Unless someone has a workaround, I'm going to close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants