bobbel

DionDesigns, thank you very much for your explanations and advice.
The WP Site that I’m trying to set up will not be public, it’s just a private project to get some hands-on experience. So search engines and their page rankings are out of scope.

The html containing the frames is just coming from the out of the box theme twentyseventeen. So it’s not really the users’s choice when doing a fresh installation of WordPress as this is the default theme.

Anyway, I managed to solve the issue. I did some more research and found out that my router has some hidden settings (not accessible in the router management UI).

Here are the details in case someone has the same issue with same kind of router:

Router: Fritz!Box 7270

The domain used was provided by dyndnss.net, which dynamically assignes the changing IP provided by the ISP to your dyndnss domain (mysite.dyndnss.net).

For this to work correctly there are some changes necessary in the Fritz!Box configuration:

Port forwarding for http requests:
Go to Fritzbox admin page > Shares > Port Forwarding

Port 80
Internal IP-Adresse of the server: 192.168.xxx.yyy
Computer: host name of the server
Protocol:TCP

On the WP Server I set up nginx as described in a previous post.

Now the missing part was a hidden setting by which the internet domain
is mapped to the static internal IP of the server. Here’s the link to the original site where I found the solution:

https://adrian-jagusch.de/2015/03/domains-abfangen-mit-der-fritzbox-als-dns-server/

As it is in german, here’s the translation:

Step 1
Go to the Fritz!Box admin page (192.168.178.1) > Home Network > Network
Click to edit the properties of your server (should be in the list)
Enable the checkbox “Always assign the same IP Address to this device”
Write down the IP-Address

Step 2
Go to System > Settings Back-up
Enter password and save the settings file to disk
Edit the file with a text editor and update following block with your domain information and the IP from step 1

landevices {
landevices {
ip = 192.168.xxx.yyy;
name = “mysite.dyndns.net”;
mac = 00:00:00:00:00:00;
medium = medium_unknown;
}
}

Add NoChecks=yes, in order to tell the admin utility to not check for changes when uploading the settings file back to the fritzbox

Language=de
NoChecks=yes
**** CFGFILE:ar7.cfg

Save changes and go to Back-up Settings > Restore Settings to upload the changed settings file. After successful upload, the Fritz!Box will restart.

Then it worked fine. So in my case it was a missing configuration step on the router. Strangely enough this isn’t mentioned in a lot of “recipes” for settings up the fritzbox for port forwarding with dynmic dns.

Thanks again to all who took the time to reply.

All, thanks for taking the time to look into this and reply.

@diondesigns: it sounds very plausible. However, I have a really basic question: How/where do I change the DNS A record? Is it something I can set on the server / router? Or is it managed by the domain provider?

I’ve set my router to always provide the same ip address for the wp server and mapped it to the domain, and set the necessary port routing for :80. Which seems to work, as the site can be accessed.

What am I missing?

Sorry, I didn’t understand. The actual URL is https://ynbx.dyndnss.net

Yes,

siteurl: https://my.site.com
home: https://my.site.com
==> Home page loads without css, as described in the beginning

if I switch it back to

siteurl: 192.168.xxx.yyy
home: 192.168.xxx.yyy
==> Page loads with css

I want to set the siteurl and home to https://my.site.com (because i suppose this is how it should be). How can I make it load the css correctly?

Is it maybe related to webserver (nginx) settings?

Here is the content of the etc\nginx\sites-available\default – in case the issue might be here

server {
listen 80 default_server;
listen [::]:80 default_server;

root /var/www/html;

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

server_name my.site.com https://www.my.site.com;

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

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

}

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

Correction: I changed it to https://my.site.com

That’s exactly what I did. I changed the site url and home to my.site.com through phpmyadmin in the db . And then the page loads with broken css.