sumithemmadi / tor-hidden-service-on-heroku Goto Github PK

Host Tor v3 Hidden Service in dark web using heroku

Try my another repository built with nodejs https://github.com/sumithemmadi/Tor-Onion-Service-On-Heroku

1 . To host your website in dark web with one click and run server on heroku.

2 . Click below Deploy to Heroku Button.

Note : Deploy with heroku Deploy button will host a demo webpage, you can not use your html file.To host your own webpage goto Manually Deploy to Heroku Session

3 . You will be navigated to Heroku Dashboard. Enter app name in App name field and click Deploy app button.

4 . Now your app is accessible over Tor.

Note :- Since,heroku has an ephemerals file system that is destroyed every time when your app restart's.so your application will generate a new .onion link everytime when your app restarts.To use your custom permanent onion link go down to Manually Deploy to Heroku.

5 . To know you .onion address click here

1 . Create a new project, for example in my case Project and go to that directory.

2 . Clone this repository with below command

heroku apps:create App-Name this command creates the application as well as a git remote, that you can use to push your code to Heroku.

Note: replace App-Name with any other name.

4 . Now add two buildpacks heroku/php and heroku-community/apt to you application.

• heroku/php

• heroku-community/apt

6 . Copy your website file's to the folder public_html
eg :- index.html,index.php [default=index.html]

7 . Copy the following files to temp/var/lib/tor/hidden_service dir

• hostname
• hs_ed25519_public_key
• hs_ed25519_secret_key

If you don't know where these files stored refer to https://2019.www.torproject.org/docs/tor-onion-service

8 . Or go down to testing session to generate tor onion addresses.

9 . Deploy your changes to heroku

If you still can't find your .onion link.
Open your heroku app
https://App-Name.herokuapp.com and click on show my .onion link.

Note : Due to herokus policies, a single web dyno is sent to sleep after 30 minutes of inactivity. This means if your application has not served any requests for 30 minutes, it is forced to sleep by heroku and has to wake up prior to serve a new request, which easily can take up to 30–40 seconds. Generally free dynos will sleep (shut down) after 30 minutes of inactivity. This is actually a feature to avoid using up your free dyno hours. To prevent Heroku app from idling add New Relic add-on. It has an availability monitor feature that will ping your site twice per minute, thus preventing the dyno from idling (Or) add Uptimerobot it is free and offers 5 min interval site checking.

Here is my app https://tor-hidden-service-on-heroku.herokuapp.com/