Welcome! Log In Create A New Profile

Advanced

Falsche Rootseite bei FQDN

Posted by chris4712 
Falsche Rootseite bei FQDN
September 09, 2020 04:25PM
Hallo liebe Leute,

ich bin ziemlich neu im Thema NGNIX, ich bitte daher um Nachsicht. Ich habe folgendes Problem. Ich habe bei uns im Firmenintranet die Kommunikationsplattform BigBlueButton installiert. Ich gehe aufgrund der Symptomatik aber davon aus, dass disese problem ngnix-spezifisch ist. Der linunx-Server ist (z.Zt. noch virtualisiert mittels Hyper v). Auf unserem Windows DNS Server, hat die ip des UbuntuRechners einen entsprechenden Eintrag.

Ich kann diese IP, sowie die entsprechende FQDN anpingen, ich denke in die Windowsdomäne muss ich den Rechner dazu nicht extra einbinden. Ich bekomme aber die entsprechende BBB Seite nur wenn ich die IP aufrufe, bei Eingabe der FQDN bekomme ich lediglich die Ngnix Infoseite? Was habe ich falsch gemacht. Die entsprechenden configs im verzeichnis sites-enabled sehen wie foglt aus, ich denke hier leigt der hun begraben.

bigbluebutton
--------------------------------------
server {
listen 80;
listen [::]:80;
server_name lcs;

access_log /var/log/nginx/bigbluebutton.access.log;

# Handle RTMPT (RTMP Tunneling). Forwards requests
# to Red5 on port 5080
location ~ (/open/|/close/|/idle/|/send/|/fcs/) {
proxy_pass http://127.0.0.1:5080;
proxy_redirect off;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

client_max_body_size 10m;
client_body_buffer_size 128k;

proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;

proxy_buffering off;
keepalive_requests 1000000000;
}

# Handle desktop sharing tunneling. Forwards
# requests to Red5 on port 5080.
location /deskshare {
proxy_pass http://127.0.0.1:5080;
proxy_redirect default;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 10m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
include fastcgi_params;
}

# BigBlueButton landing page.
location / {
root /var/www/bigbluebutton-default/b;
index index.html index.htm;
expires 1m;
}

# Include specific rules for record and playback
include /etc/bigbluebutton/nginx/*.nginx;

#error_page 404 /404.html;

# Redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /var/www/nginx-default;
}
}


default
---------------------
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;

# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;

root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php7.0-cgi alone:
# fastcgi_pass 127.0.0.1:9000;
# # With php7.0-fpm:
# fastcgi_pass unix:/run/php/php7.0-fpm.sock;
#}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}


Vielen DANK für Hilfestellung i.V.


lg

chris
Re: Falsche Rootseite bei FQDN
September 09, 2020 04:26PM
Hallo liebe Leute,

ich bin ziemlich neu im Thema NGNIX, ich bitte daher um Nachsicht. Ich habe folgendes Problem. Ich habe bei uns im Firmenintranet die Kommunikationsplattform BigBlueButton installiert. Ich gehe aufgrund der Symptomatik aber davon aus, dass disese problem ngnix-spezifisch ist. Der linunx-Server ist (z.Zt. noch virtualisiert mittels Hyper v). Auf unserem Windows DNS Server, hat die ip des UbuntuRechners einen entsprechenden Eintrag.

Ich kann diese IP, sowie die entsprechende FQDN anpingen, ich denke in die Windowsdomäne muss ich den Rechner dazu nicht extra einbinden. Ich bekomme aber die entsprechende BBB Seite nur wenn ich die IP aufrufe, bei Eingabe der FQDN bekomme ich lediglich die Ngnix Infoseite? Was habe ich falsch gemacht. Die entsprechenden configs im verzeichnis sites-enabled sehen wie foglt aus, ich denke hier leigt der hun begraben.

bigbluebutton
--------------------------------------
server {
listen 80;
listen [::]:80;
server_name lcs;

access_log /var/log/nginx/bigbluebutton.access.log;

# Handle RTMPT (RTMP Tunneling). Forwards requests
# to Red5 on port 5080
location ~ (/open/|/close/|/idle/|/send/|/fcs/) {
proxy_pass http://127.0.0.1:5080;
proxy_redirect off;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

client_max_body_size 10m;
client_body_buffer_size 128k;

proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;

proxy_buffering off;
keepalive_requests 1000000000;
}

# Handle desktop sharing tunneling. Forwards
# requests to Red5 on port 5080.
location /deskshare {
proxy_pass http://127.0.0.1:5080;
proxy_redirect default;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 10m;
client_body_buffer_size 128k;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
include fastcgi_params;
}

# BigBlueButton landing page.
location / {
root /var/www/bigbluebutton-default/b;
index index.html index.htm;
expires 1m;
}

# Include specific rules for record and playback
include /etc/bigbluebutton/nginx/*.nginx;

#error_page 404 /404.html;

# Redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /var/www/nginx-default;
}
}


default
---------------------
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
listen 80 default_server;
listen [::]:80 default_server;

# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;

root /var/www/html;

# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;

server_name _;

location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php7.0-cgi alone:
# fastcgi_pass 127.0.0.1:9000;
# # With php7.0-fpm:
# fastcgi_pass unix:/run/php/php7.0-fpm.sock;
#}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
# listen 80;
# listen [::]:80;
#
# server_name example.com;
#
# root /var/www/example.com;
# index index.html;
#
# location / {
# try_files $uri $uri/ =404;
# }
#}


Vielen DANK für Hilfestellung i.V.


lg

chris
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 57
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready