Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6549733
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T12:07:45+00:00 2026-05-25T12:07:45+00:00

I have a VMWare virtual Linux server on which i installed a Java EE

  • 0

I have a VMWare virtual Linux server on which i installed a Java EE web application. i access the server via SSH.

my question is how can i run the remote web app through ssh?

what i did is start remote tomcat server over ssh
then in my browser i invoked this address :

 http://<ssh-server-host>:8080

the connection took very long and my firefox can’t establish connection b/c it takes too long.

is there a clean way to run a web app over ssh?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T12:07:45+00:00Added an answer on May 25, 2026 at 12:07 pm

    What you are doing can also be called ssh tunneling. It has the advantage that your traffic will be encrypted, but it will also be a bit slower (encryption/decryption being done by ssh), and more resource intensive. Besides, the tunnel will have to stay open in order to access the endpoint.

    The technique is specially useful if you are not interested in making a service remotely accessible, but still want to use privately.

    For example, I have a couchdb server listening on localhost:5984, in my host “server1”
    I can make that port locally accessible in port 22222 in my desktop computer, by doing:

    desktop $ ssh -f user@server1 -L localhost:22222:server1:5984 -N
    

    This way I can access my remote couchdb:

    curl -X GET http://localhost:22222
    

    And that even though the remote couchdb server is only listening to local connections. The SSH tunnel makes the magic.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.