Report post You have 30 minutes to complete this form before the CAPTCHA will expire. Security image * Required field JavaScript is required to view this page. Either you do not have JavaScript enabled in your web browser, you do not have cookies enabled in your web browser, or this website is misconfigured such that cookies do not save correctly. This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="Owncast installation issue"]931[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><input class="cms_keep_ui_controlled" size="45" title="[quote param="2"]Regarding what&#039;s in the title bar (I assume you also mean URL bar), it&#039;s generally expected that whatever you type into the URL bar will stay there regardless of what webpage Apache sends back. The URL bar will only change if you do something like send an HTTP redirect header to actually redirect the web browser to a different URL, or include an HTML meta tag to do that. Otherwise, the configuration and fallbacks that Apache has in place are transparent to the client-side web browser. The browser doesn&#039;t know which Apache config file or Apache virtual hosts it&#039;s receiving data through. I think I&#039;ve spotted what you did wrong. This is your current owncast-le-ssl.conf file: <comcode-code scroll="1">ServerName live.seth.wtf ServerAdmin seth@seth.wtf ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/live.seth.wtf/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/live.seth.wtf/privkey.pem# Proxy traffic to/from Owncast. ProxyRequests Off ProxyPreserveHost On AllowEncodedSlashes NoDecodeOrder deny,allow Allow from allProxyPass / http://localhost:8080/ ProxyPassReverse / http://localhost:8080/ RequestHeader set X-Forwarded-Proto &quot;https&quot; RequestHeader set X-Forwarded-Port &quot;443&quot; # Ensure websocket connections are also proxied. RewriteEngine On RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR] RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC] RewriteRule .* ws://127.0.0.1:8080%{REQUEST_URI} [P,QSA,L] </comcode-code> You&#039;ve correctly identified that all traffic is being redirected (or, rather, proxied) to port 8080. The reason is because you put that configuration <i>after</i> the closing tag, which means it&#039;s just general configuration you&#039;ve applied to your server (any files before it are applied first, hence why the HTTP to HTTPS redirects are working, but the configuration is still being applied). The "additional configuration" from Step 9 of my <a class="user_link" href="https://nerdonthestreet.com/wiki?find=Install+an+Owncast+Streaming+Server" rel="nofollow noopener" target="_top">guide</a> is supposed to go <i>inside</i> of the<!--filtered; no Subject to a more liberal HTML filter-->&hellip;<!--filtered; no Subject to a more liberal HTML filter-->block. That will restrict the configuration to only traffic destined for that virtual host. You can see where I inserted it at <a class="user_link" href="https://nerdonthestreet.com/episode/tech/owncast-self-hosted-streaming-chat?t=1030" rel="nofollow noopener" target="_top">this timestamp of my video</a>&ndash; I actually put it before the SSL certificate lines, although off the top of my head, I think putting it after those lines would behave the same, as long as it&#039;s inside of the VirtualHost block. Let me know if that helps!<br />[/quote]" type="button" value="quote Comcode tag (dbl-click to edit/delete)" /><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="Owncast installation issue"]931[/post], by jacobgkau [quote="2"] [semihtml]Regarding what's in the title bar (I assume you also mean URL bar), it's generally expected that whatever you type into the URL bar will stay there regardless of what webpage Apache sends back. The URL bar will only change if you do something like send an HTTP redirect header to actually redirect the web browser to a different URL, or include an HTML meta tag to do that. Otherwise, the configuration and fallbacks that Apache has in place are transparent to the client-side web browser. The browser doesn't know which Apache config file or Apache virtual hosts it's receiving data through. I think I've spotted what you did wrong. This is your current owncast-le-ssl.conf file: [codebox]ServerName live.seth.wtf ServerAdmin seth@seth.wtf ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/live.seth.wtf/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/live.seth.wtf/privkey.pem# Proxy traffic to/from Owncast. ProxyRequests Off ProxyPreserveHost On AllowEncodedSlashes NoDecodeOrder deny,allow Allow from allProxyPass / http://localhost:8080/ ProxyPassReverse / http://localhost:8080/ RequestHeader set X-Forwarded-Proto "https" RequestHeader set X-Forwarded-Port "443" # Ensure websocket connections are also proxied. RewriteEngine On RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR] RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC] RewriteRule .* ws://127.0.0.1:8080%{REQUEST_URI} [P,QSA,L] [/codebox] You've correctly identified that all traffic is being redirected (or, rather, proxied) to port 8080. The reason is because you put that configuration [i]after[/i] the closing tag, which means it's just general configuration you've applied to your server (any files before it are applied first, hence why the HTTP to HTTPS redirects are working, but the configuration is still being applied). The "additional configuration" from Step 9 of my [url="https://nerdonthestreet.com/wiki?find=Install+an+Owncast+Streaming+Server"]guide[/url] is supposed to go [i]inside[/i] of the<virtualhost>...</virtualhost>block. That will restrict the configuration to only traffic destined for that virtual host. You can see where I inserted it at [url="https://nerdonthestreet.com/episode/tech/owncast-self-hosted-streaming-chat?t=1030"]this timestamp of my video[/url]-- I actually put it before the SSL certificate lines, although off the top of my head, I think putting it after those lines would behave the same, as long as it's inside of the VirtualHost block. Let me know if that helps![/semihtml] [/quote] //// PUT YOUR REPORT BELOW \\\\ View all Use of this website implies that you agree to the website rules and privacy policy. Statistics Users online: Details jacobgkau, 17 guests Usergroups: Administrators Forum statistics: 148 topics, 639 posts, 633 members Our newest member is OfflineInfluencer83 Birthdays: shimatani (41)