The page of jekyll-admin is blank

Description:

Tell us a bit about yourself:

• Version of JekyllAdmin I'm using <HINT: use bundle show to check>:
  jekyll-admin (0.8.1)
• Version of Jekyll I'm using <HINT: use bundle show to check>:
  jekyll 3.8.5
• Version of NodeJS I'm using <HINT: use node -v to check>:
  Not using node
• Operating System <e.g. OS X, Windows>:
  CentOS Linux release 7.6.1810 (Core) (VPS)
• Browser <e.g, Safari, Chrome>:
  Chrome

Steps to reproduce:

I expected the following:

1. jekyll is installed correctly；
2. But the jekyll‘s default port is 4000, so I installed the nginx, and then proxy the data from 4000 to 80 port. The configure of nginx is as follows:

server {
    listen 80;
    server_name 47.107.164.222;
    location / {
        proxy_pass http://localhost:4000;
    }
}

and when I enter IP (instead of IP:4000) in the browser, the page of Jekyll is displayed normally, as follows:

3. When I installed Jekyll-admin and typed IP/admin in the browser, the page was blank.

No information was displayed, as well as error.

But got the following, instead:

A blank page

Other details:

So how to solve this problem?

[yangjianyao]

I have same problem

[mertkahyaoglu]

Is there any error on developer console? Could you share it if there is?

[yangjianyao]

When jekyll was just started, jekyll and jekyll-admin pages are both OK.
After a while, when I used jekyll-admin again, I found that it didn't work and showed blank.
Sorry,I don't know where the relevant log is.

[franciscoprado]

I got a 404 page when accessing /admin, neither blank page or anything else. Running on Linux Mint 19.1.

[lexoyo]

hi all
as @mertkahyaoglu asked, if you get a blank page, please open the developer console in your browser and provide the errors you see (network or JS)
thx

[Taubin]

I'm having the same issue here, blank page.

When running bundle serve, I get the following:

bundle exec jekyll serve
Configuration file: /mnt/d/OneDrive/taubincc/_config.yml
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/apiable.rb:6: warning: already initialized constant JekyllAdmin::APIable::CONTENT_FIELDS
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/apiable.rb:6: warning: previous definition of CONTENT_FIELDS was here
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/data_file.rb:3: warning: already initialized constant JekyllAdmin::DataFile::METHODS_FOR_LIQUID
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/data_file.rb:3: warning: previous definition of METHODS_FOR_LIQUID was here
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/data_file.rb:4: warning: already initialized constant JekyllAdmin::DataFile::EXTENSIONS
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/data_file.rb:4: warning: previous definition of EXTENSIONS was here
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/directory.rb:12: warning: already initialized constant JekyllAdmin::Directory::TYPE
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/directory.rb:12: warning: previous definition of TYPE was here
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/server/data.rb:4: warning: already initialized constant JekyllAdmin::Server::EXTENSIONS
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/server/data.rb:4: warning: previous definition of EXTENSIONS was here
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/server.rb:3: warning: already initialized constant JekyllAdmin::Server::ROUTES
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/server.rb:3: warning: previous definition of ROUTES was here
/mnt/d/OneDrive/taubincc/_plugins/jekyll-admin/jekyll-admin/static_server.rb:5: warning: already initialized constant JekyllAdmin::StaticServer::MUST_BUILD_MESSAGE
/var/lib/gems/2.5.0/gems/jekyll-admin-0.8.1/lib/jekyll-admin/static_server.rb:5: warning: previous definition of MUST_BUILD_MESSAGE was here
            Source: /mnt/d/OneDrive/taubincc
       Destination: /mnt/d/OneDrive/taubincc/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       Jekyll Feed: Generating feed for posts
                    done in 0.528 seconds.
                    Auto-regeneration may not work on some Windows versions.
                    Please see: https://github.com/Microsoft/BashOnWindows/issues/216
                    If it does not work, please upgrade Bash on Windows or run Jekyll with --no-watch.
 Auto-regeneration: enabled for '/mnt/d/OneDrive/taubincc'
  JekyllAdmin mode: production
    Server address: http://127.0.0.1:4000/
  Server running... press ctrl-c to stop.
[2019-05-01 09:23:14] ERROR `/favicon.ico' not found.

Nothing in the console at all, and network shows a 404.

Config.yaml

# Welcome to Jekyll!
#
# This config file is meant for settings that affect your whole blog, values
# which you are expected to set up once and rarely edit after that. If you find
# yourself editing this file very often, consider using Jekyll's data files
# feature for the data you need to update frequently.
#
# For technical reasons, this file is *NOT* reloaded automatically when you use
# 'bundle exec jekyll serve'. If you change this file, please restart the server process.

# Site settings
# These are used to personalize your new site. If you look in the HTML files,
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
title: redacted
# email: your-email@example.com
description: >- # this means to ignore newlines until "baseurl:"
  redacted is my personal blog. Expect rants and raves.
baseurl: "" # the subpath of your site, e.g. /blog
url: "redacted" # the base hostname & protocol for your site, e.g. http://example.com
twitter_username: redacted
github_username:  redacted

# Build settings
markdown: kramdown
theme: minima
plugins:
  - jekyll-feed
  - jekyll-admin

# Exclude from processing.
# The following items will not be processed, by default. Create a custom list
# to override the default setting.
# exclude:
#   - Gemfile
#   - Gemfile.lock
#   - node_modules
#   - vendor/bundle/
#   - vendor/cache/
#   - vendor/gems/
#   - vendor/ruby/

Gemfile

source "https://rubygems.org"

# Hello! This is where you manage which Jekyll version is used to run.
# When you want to use a different version, change it below, save the
# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
#
#     bundle exec jekyll serve
#
# This will help ensure the proper Jekyll version is running.
# Happy Jekylling!
gem "jekyll", "~> 3.8.5"

# This is the default theme for new Jekyll sites. You may change this to anything you like.
gem "minima", "~> 2.0"

# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
# uncomment the line below. To upgrade, run `bundle update github-pages`.
# gem "github-pages", group: :jekyll_plugins

# If you have any plugins, put them here!
group :jekyll_plugins do
  gem "jekyll-feed", "~> 0.6"
  gem 'jekyll-admin', group: :jekyll_plugins
end

# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]

# Performance-booster for watching directories on Windows
gem "wdm", "~> 0.1.0" if Gem.win_platform?

EDIT:

I was able to figure out my issue. I had copied the jekyll-admin folder in with the jekyll and jekyll-admin.rb file into my plugins folder. Deleting the jekyell-admin folder from within the jekyll-admin folder corrected my issue.

My current structure is

|_ plugins
| jekyll-admin
|_ jekyll
|_ jekyll-admin.rb

This is working properly.

[20chan]

I have same problem.
When I send http request to /_api/configuration/ with Referer header, it just returns 403 stauts. Without Referer header it works fine.

[lexoyo]

@20chan this is a good clue thx
What makes you think this is the cause of this issue?
What errors do you have in the console if any?

[theS1LV3R]

Same for me, when i try to use jekyll admin i just get a blank page with the following in the dev. console:

GET https://4000-dot-6762651-dot-devshell.appspot.com/_api/configuration 403

I also don't have a folder named _api in my root folder

[tomscytale]

jekyll 4.0.0
jekyll-admin 0.9.6

I run bundle exec jekyll serve on my server

I can access the jekyll-admin site just fine over a ssh port forward from my laptop.

I then try access jekyll-admin via a nginx proxy:

    location ^~ /admin {
        proxy_pass http://127.0.0.1:4000/admin;

        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $http_host;

This only shows a blank page. The (edited) nginx logs show this :

 1.2.3.4 - - [30/Sep/2019:18:18:27 +0000] "GET /admin/ HTTP/1.1" 200 385 "-"
 1.2.3.4 - - [30/Sep/2019:18:18:27 +0000] "GET /admin/styles.css HTTP/1.1" 200 18253 "http://www.foo.com/admin/"
 1.2.3.4 - - [30/Sep/2019:18:18:27 +0000] "GET /admin/059514c92565e4045da1a69525dd9ec0.ttf HTTP/1.1" 200 138900 "http://www.foo.com/admin/styles.css"
 1.2.3.4 - - [30/Sep/2019:18:18:28 +0000] "GET /admin/bundle.js HTTP/1.1" 200 739312 "http://www.foo.com/admin/"
 1.2.3.4 - - [30/Sep/2019:18:18:28 +0000] "GET /_api/configuration HTTP/1.1" 404 153 "http://www.foo.com/admin/"
 1.2.3.4 - - [30/Sep/2019:18:18:29 +0000] "GET /admin/favicon.ico HTTP/1.1" 200 5430 "-"

Note the 404 for /_api/configuration

The browser console does not show any errors.

I tried this a few weeks ago and I got a 403 like @20chan - it looks like something changed with the latest release.
I tried removing the Referrer header and resending - still got a 404

I then compare with what happens when I access the page over the ssh port forward:

As you can see /_api/configuration gets a 202 and the page continues to load several other assets.

Comparing the headers I see that when accessed over the ssh tunnel the request for /_api/configuration sends a cookie with the content io=.......; connect.sid=.......
Is this a security token?
Is there a way I can configure jekyll-admin to set this cookie when accessed via the nginx proxy?

[tomscytale]

Got it working!

     location ^~ /admin {
         proxy_pass http://127.0.0.1:4000/admin;

         auth_basic "Administration";
         auth_basic_user_file /etc/nginx/htpasswd;

         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header Host $http_host;
     }
     location ^~ /_api {
         proxy_pass http://127.0.0.1:4000/_api;

         auth_basic "Administration";
         auth_basic_user_file /etc/nginx/htpasswd;

         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header X-Forwarded-Proto $scheme;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header Host $http_host;
    }

Ideally we'd combine the blocks using a regex, but I can't get it working - I've tried

     location ~ ^/(admin|_api)(/.*)? {
         proxy_pass http://127.0.0.1:4000/$1;

        ....

(this block needs to come before regex location matches for the main site)
but for some reason .js and .css files get their mime type set to text/html when I do this.

And you must enable some kind of authentication - I've used http basic auth

         auth_basic "Administration";
         auth_basic_user_file /etc/nginx/htpasswd;

See the nginx docs