change listening address/interface

Open
#649 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
networking

Research direction

Start with application.yml and the server startup/configuration path that consumes its environments.production.server settings. Reproduce with 127.0.0.1 and port 7373, then verify with netstat or sockstat that Streama binds only to the loopback interface rather than all available addresses.

Written by the indexing model from the issue text.

Description

Hosting More Info required
Issue description

I came across a problem I couldn't figure out yet (without modifying the source code). Is it not possible to change the listening address or interface of the application? I dislike the idea that Streama is accessible without a proxy from literally any available IP address. My goal is to lock down Streama to 127.0.0.1 and proxy all requests with my web server.

I already managed to change the default port as 8080 is already reserved on my server for something else.

This is my application.yml

environments:
    production:
        server:
            hostname: 127.0.0.1
            host: 127.0.0.1
            port: 7373

Except the port the other options are completely ignored.

Steps to Reproduce
  1. Create this application.yml file.
  2. Start Streama
  3. Look for open ports with either sockstat or netstat.
Expected Behavior

That Strema doesn't take over all interfaces and is accessible from the outside via IP address. Using a proxy is preferred behavior.

Actual Behavior

Streama listens on everything where it can get its greedy hands on.

Environment Information
  • Operating System: FreeBSD 11.2-RELEASE
  • Streama version: 1.6.0-RC7
  • Custom streama build, describe customizations or provide link to fork (If Applicable): No
  • Container Version (If Applicable): No

EDIT!: At the moment I blocked the port using pf (firewall) as workaround. I really don't want any open ports other than the web server and SSH.

Dominant language
JavaScript
Stars
9.8k
Forks
978
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from streamaserver/streama

All issues in streamaserver/streama

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.