Apache Welcome Page Question/Problem
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
No repository files or tests are named. Start by checking the Apache VirtualHost configuration and its proxy target at localhost:8080, then compare access by local IP with the configured host. Done means the local intranet address serves Streama instead of Apache's welcome page.
Written by the indexing model from the issue text.
Description
Hello everyone,
I am very interested in deploying a LOCAL web server with Streama, in order to post videos from my company to our local intranet. So the idea is for our users to access the server locally and not from the internet, meaning no certificates nor public records are needed, at least in theory.
I tried following this guide, knowing it's not an official one:
https://www.howtoforge.com/tutorial/how-to-install-streama-on-centos-7/
So what I omit on this guide is this step:
<VirtualHost *:80>
ServerName streama.yourdomain.com
Redirect permanent / https://streama.yourdomain.com/
TransferLog /var/log/httpd/streama.yourdomain.com_access.log
ErrorLog /var/log/httpd/streama.yourdomain.com_error.log
<VirtualHost *:443>
ServerName streama.yourdomain.com
ServerAdmin email@yourdomain.com
SSLEngine On
SSLCertificateFile /etc/letsencrypt/live/streama.yourdomain.com/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/streama.yourdomain.com/privkey.pem
ProxyPreserveHost On
ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/
TransferLog /var/log/httpd/streama.yourdomain.com_ssl_access.log
ErrorLog /var/log/httpd/streama.yourdomain.com_ssl_error.log
Configuration on port 443 was removed, as we are not using any certificates, creation of certificates was also omit and port 80 redirect permanent option was also deleted.
After all that, when accessing local IP address on intranet browsers I see the welcome page for Apache but not the streama website, anything you might recommend to check?
Salutes!
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 978
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from streamaserver/streama
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
streamaserver/streama#1164 ·
-
API calls Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
streamaserver/streama#1162 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1161 ·
-
Java issue Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1160 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1157 · 1 comment ·
All issues in streamaserver/streama
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100