css and other asset resources loading failed

[Harrypotterrrr]

Environment

• Minimal Mistakes version: I use academicpages

• Ruby gem or remote theme version:
  ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]
  gem 2.7.6

• Jekyll version: 3.8.7

• Git repository URL: https://github.com/Harrypotterrrr/Homepage

• GitHub Pages hosted (if yes provide URL to site):

• Operating system: Linux ubuntu6-1 4.15.0-29-generic Hotlinked images #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Expected behavior

Hi, I am using academicpages, a repository forked from this minimal-misktake which is very suitable to the academic propose. I am trying to debug and modify my homepage by using bundle exec jekyll serve --host 0.0.0.0 --port 8445 --incremental on the remote server. Note that this remote server is the one with inner IP and cannot be accessed from outside, so I use port forward technique to propagate the port to the public server IP by using ssh -NfR 8445:localhost:8445 root@106.13.xx.xx.

I manage to see all the text of my homepage, while I fail to load any CSS and asset images etc. As the below figure shows:

You can see the request is http://0.0.0.0:8445/assets/css/main.css. I change 0.0.0.0 to my public server IP 106.13.xx.xx, that is
http://106.13.xx.xx:8445/assets/css/main.css, I successfully get the main.css file as the following image shows, which means port forward success.

So I turn to the _config.yml to see if I could modify host or something else to direct assets request to 106.13.xx.xx instead of 0.0.0.0 but finally I failed.

Struggling for hours, I have to ask you for help for I am a newbie in front-end tech.
Hope I make my problem clear and easy to understand. I just wanna test my modification and debug on that remote server, which has an inner IP address and can not be accessed outside. I have no problem with deploying it to Github.
Thanks for your help in advance!

[iBug]

This is an upstream issue. Jekyll overrides site.url when running in serve mode, which by default is http://127.0.0.1:4000 and changes with your host/port settings.

If you're using SSH forwarding, just launch Jekyll with default host / port and let SSH forward 4000:127.0.0.1:4000 and it should behave normally.

In short, drop the --host option, it's unnecessary.

[Harrypotterrrr]

@iBug Hi, appreciate your instant reply. I tried to use default host and port: bundle exec jekyll serve --incremental but nothing seems change. I still fail to get CSS and other assets files.

I use this command to forward SSH port: ssh -NfR 4000:localhost:4000 root@106.13.xx.xx
Here is what I see in my chrome browser. sad.. 😢

[iBug]

Are you sure your SSH client is running properly? With a Linux machine, you can check if there's an ssh process listening on port 4000 with the command netstat -tlpn and look into its output.

In addition, with SSH forwarding enabled, you shouldn't visit the server's address directly, but only http://127.0.0.1:4000/, as SSH will handle all the traffic.

Anyways, this is not a theme-specific issue, so I'd suggest that you seek help over on Jekyll Talk where people with more expertise can assist you.

[mmistakes]

Closing as this is an environment/upstream issue and not something impacted by the theme.

[Harrypotterrrr]

@iBug I confirm SSH client runs properly. I use code-server on this inner remote server, and I modify codes remotely on my local PC. I use netstat- nultp commands and the process seems to work well as below.

I use remote port forwarding, which means I could visit the remote server which has the public IP and request for resources on the remote private server.
This is not a theme-specific issue, anyway, thanks for your reply.

[Harrypotterrrr]

Generally, I think the problem is, just take avatar.jpg as an example, jekyll generate index.html which contains the assets file withhttp://localhost:4000/assets/avatar.jpg:4000 link. But this should be http://106.13.xx.xx:4000/assets/avatar.jpg:4000. Because I can successfully get avatar.jpg through the second URL, but the first one with localhost I failed.

[iBug]

You should have used local forwarding, i.e. ssh -L, not ssh -R, which would do the reverse. With ssh -L, you can visit your local port and SSH will access the remote port.

Check this question for better understanding of SSH port forwarding.

[Harrypotterrrr]

@iBug Thanks a lot. I used to use remote ssh forwarding to fetch remote resources, eg. code-server, jupyter etc. Besides using remote forward on the inner server with ssh -NfR, I run ssh -NfL 4000:localhost:4000 root@106.13.xx.xx to forward local to the public remote server. Now everything works well. Appreciate your reply and documentation sincerely.