Hugoplate rendering issue

Using Themes
1

I seem to be having a rendering issue when trying to run my site using the theme Hugoplate.

When I run the development server everything renders properly, but when I fully deploy the site it looks like this:

Screenshot_20260109-234924793
Screenshot_20260109-2349247931080×2340 61.7 KB

Does anyone know what may be causing this or how to fix it? Any help/advice is appreciated, this is my first site and I’m fairly new to hugo.

2

You are more likely to receive a prompt and accurate response if you post a link to your project’s Git repository.

See Requesting Help.

Let us see your code

Include a link to the source code repository of your project, because we really need the context of seeing your templates and partials to be able to help you. It is trivial to do a quick git clone on your repo, then run hugo server in your project, to help you out. On the other hand, recreating your code from screenshots, or sort of guessing at it, is not.

If you can’t share your repository for whatever reason, consider creating a dummy repo that you can share, which reproduces the problem you’re experiencing.

4

you deployed the site that was generated using hugo server. that won’t work.

  • make sure your baseURL is correct
  • delete your publishDir ( default is public)
  • use hugo to generate a deployable site
6

Your base url at hugo.toml is localhost:1313 you have to change it to novacircus.com.

7

I changed the baseURL parameter to novacircus[dot].com instead of https://novacircus.com, but the site still shows as localhost:1313 when I deploy.

Here is the link to my site’s Git repository sans the assets, content, and resources folders as those were too large to upload.

8

the correct value for the baseurl is https://novacircus.com with the protocol. BUT your problem is NOT the setting in your hugo.toml.

its the way you build and deploy

as stated before: your deployment process creates the site using the hugo server command, which will - ignoring the baseURL setting - use localhost

some extract von your deployed homepage:

  • the livereload tells it was created by hugo server not hugo.
  • the version does not match version stated in the build scripts and configs of your repo (139)

→ so your build and deploy seems different from all the scripts and configs in your repo

<!doctype html>
<html itemscope class="system" lang="en-us" itemtype="http://schema.org/WebPage">
  <head>
	<meta name="generator" content="Hugo 0.150.1"><script src="/livereload.js?mindelay=10&amp;v=2&amp;port=1313&amp;path=livereload" data-no-instant defer></script>
    <meta charset="utf-8" />
...
<base href="//localhost:1313/" />
...

I quickly scanned the repo and there are a bunch of build script, but all seem to use just hugo (no server).

How do you deploy your site?

  • if you just push a local created public directory, check my previous comment.

  • if you build and publish your site using a CI script

    • check the ci scripts actually used
    • and the build logs.

    guess there’s a hint where it comes from.

1 Like
9

Thanks, I will add https back to the baseURL parameter. I’m curious how you can tell what I used to deploy. I was using hugo server before your direction to use hugo; but after your last message, I used hugo to deply. This is a local deployment I am manually pushing the resulting contents of the public to the web server after I run hugo. I removed the entire public folder before I ran hugo. Then I moved its contents to the web server manually.

10

check the result homepage.

  • the live reload script is gone. so now you use hugo only good.

  • you set base to localhost

  • your meta tags still use //localhost

  • many hrefs point to //...

  • many use /...

i would remove the <base href="//localhost:1313/" /> or the code that generates this.

check the html stuff generated in your public directory…

there are many href or other tags referencing that don’t do what you want

maybe it’s time to share a runnable repo with some content