Problem with link to page [freeze flask]

https://reynaldosergiogonzalez.netlify.app/

I am trying to make a website using Flask with the Freeze package to make static files.
I am following this tutorial:

The thing is this tutorial was made to create a single page website.
I have an about page linked from my home page, but when the link is clicked it only renders the html code.
Does anyone know which freeze function I should be using and how to properly set up the links?

1:52:12 PM: Build ready to start
1:52:16 PM: build-image version: 342853e31ef590be8195dfbea64bbc4657de7b6b
1:52:16 PM: build-image tag: v3.3.16
1:52:16 PM: buildbot version: 0ffb969a1fc5a7aa9d2a93dd77dd40a990576807
1:52:16 PM: Fetching cached dependencies
1:52:16 PM: Starting to download cache of 79.4MB
1:52:17 PM: Finished downloading cache in 795.377556ms
1:52:17 PM: Starting to extract cache
1:52:20 PM: Finished extracting cache in 3.423115699s
1:52:20 PM: Finished fetching cache in 4.240550362s
1:52:20 PM: Starting to prepare the repo for build
1:52:21 PM: Preparing Git Reference refs/heads/master
1:52:22 PM: Starting build script
1:52:22 PM: Installing dependencies
1:52:22 PM: Python version set to 2.7
1:52:23 PM: Started restoring cached node version
1:52:26 PM: Finished restoring cached node version
1:52:27 PM: v10.21.0 is already installed.
1:52:28 PM: Now using node v10.21.0 (npm v6.14.4)
1:52:28 PM: Started restoring cached build plugins
1:52:28 PM: Finished restoring cached build plugins
1:52:28 PM: Attempting ruby version 2.6.2, read from environment
1:52:29 PM:
1:52:29 PM: ** WARNING **
1:52:29 PM: Using custom ruby version 2.6.2, this will slow down the build.
1:52:29 PM: To ensure fast builds, set the RUBY_VERSION environment variable, or .ruby-version file, to an included ruby version.
1:52:29 PM: Included versions: 2.7.1
1:52:29 PM:
1:52:29 PM: Required ruby-2.6.2 is not installed - installing.
1:52:30 PM: Searching for binary rubies, this might take some time.
1:52:30 PM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/16.04/x86_64/ruby-2.6.2.tar.bz2
1:52:30 PM: Checking requirements for ubuntu.
1:52:31 PM: Requirements installation successful.
1:52:31 PM: ruby-2.6.2 - #configure
1:52:31 PM: ruby-2.6.2 - #download
1:52:32 PM: No checksum for downloaded archive, recording checksum in user configuration.
1:52:32 PM: ruby-2.6.2 - #validate archive
1:52:39 PM: ruby-2.6.2 - #extract
1:52:43 PM: ruby-2.6.2 - #validate binary
1:52:44 PM: ruby-2.6.2 - #setup
1:52:46 PM: ruby-2.6.2 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.6.2@global
1:52:46 PM: ruby-2.6.2 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems…
1:52:46 PM: ruby-2.6.2 - #generating global wrappers…
1:52:46 PM: ruby-2.6.2 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.6.2
1:52:47 PM: ruby-2.6.2 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list
1:52:47 PM: ruby-2.6.2 - #generating default wrappers…
1:52:48 PM: Using /opt/buildhome/.rvm/gems/ruby-2.6.2
1:52:48 PM: Using ruby version 2.6.2
1:52:49 PM: Using PHP version 5.6
1:52:49 PM: Installing pip dependencies
1:52:49 PM: Started restoring cached pip cache
1:52:49 PM: Finished restoring cached pip cache
1:52:52 PM: DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
1:52:52 PM: Collecting click==7.1.2
1:52:52 PM: Using cached click-7.1.2-py2.py3-none-any.whl (82 kB)
1:52:52 PM: Collecting Flask==1.1.2
1:52:52 PM: Using cached Flask-1.1.2-py2.py3-none-any.whl (94 kB)
1:52:52 PM: Collecting Flask-WTF==0.14.3
1:52:52 PM: Using cached Flask_WTF-0.14.3-py2.py3-none-any.whl (13 kB)
1:52:52 PM: Collecting Frozen-Flask==0.15
1:52:52 PM: Using cached Frozen_Flask-0.15-py2.py3-none-any.whl (20 kB)
1:52:52 PM: Collecting itsdangerous==1.1.0
1:52:52 PM: Using cached itsdangerous-1.1.0-py2.py3-none-any.whl (16 kB)
1:52:53 PM: Collecting Jinja2==2.11.2
1:52:53 PM: Using cached Jinja2-2.11.2-py2.py3-none-any.whl (125 kB)
1:52:53 PM: Collecting MarkupSafe==1.1.1
1:52:53 PM: Using cached MarkupSafe-1.1.1-cp27-cp27mu-manylinux1_x86_64.whl (24 kB)
1:52:53 PM: Collecting Werkzeug==1.0.1
1:52:53 PM: Using cached Werkzeug-1.0.1-py2.py3-none-any.whl (298 kB)
1:52:53 PM: Collecting WTForms==2.3.1
1:52:53 PM: Using cached WTForms-2.3.1-py2.py3-none-any.whl (169 kB)
1:52:53 PM: Installing collected packages: click, itsdangerous, Werkzeug, MarkupSafe, Jinja2, Flask, WTForms, Flask-WTF, Frozen-Flask
1:52:54 PM: Successfully installed Flask-1.1.2 Flask-WTF-0.14.3 Frozen-Flask-0.15 Jinja2-2.11.2 MarkupSafe-1.1.1 WTForms-2.3.1 Werkzeug-1.0.1 click-7.1.2 itsdangerous-1.1.0
1:52:54 PM: Pip dependencies installed
1:52:54 PM: 5.2 is already installed.
1:52:54 PM: Using Swift version 5.2
1:52:54 PM: Started restoring cached go cache
1:52:54 PM: Finished restoring cached go cache
1:52:54 PM: Installing Go version 1.12
1:53:00 PM: unset GOOS;
1:53:00 PM: unset GOARCH;
1:53:00 PM: export GOROOT=’/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64’;
1:53:00 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:{PATH}"; 1:53:00 PM: go version >&2; 1:53:00 PM: export GIMME_ENV="/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env" 1:53:00 PM: go version go1.12 linux/amd64 1:53:00 PM: Installing missing commands 1:53:00 PM: Verify run directory 1:53:01 PM: ​ 1:53:01 PM: ┌─────────────────────────────┐ 1:53:01 PM: │ Netlify Build │ 1:53:01 PM: └─────────────────────────────┘ 1:53:01 PM: ​ 1:53:01 PM: ❯ Version 1:53:01 PM: @netlify/build 2.0.10 1:53:01 PM: ​ 1:53:01 PM: ❯ Flags 1:53:01 PM: deployId: 5eea665c423e240007020dfa 1:53:01 PM: mode: buildbot 1:53:01 PM: ​ 1:53:01 PM: ❯ Current directory 1:53:01 PM: /opt/build/repo 1:53:01 PM: ​ 1:53:01 PM: ❯ Config file 1:53:01 PM: No config file was defined: using default values. 1:53:01 PM: ​ 1:53:01 PM: ❯ Context 1:53:01 PM: production 1:53:01 PM: ​ 1:53:01 PM: ┌────────────────────────────────┐ 1:53:01 PM: │ 1. Build command from settings │ 1:53:01 PM: └────────────────────────────────┘ 1:53:01 PM: ​ 1:53:01 PM: python freeze.py
1:53:02 PM: /opt/buildhome/python2.7/local/lib/python2.7/site-packages/flask_frozen/init.py:199: MimetypeMismatchWarning: Filename extension of u’about’ (type application/octet-stream) does not match Content-Type: text/html; charset=utf-8
1:53:02 PM: return set(page.url for page in self.freeze_yield())
1:53:02 PM: ​
1:53:02 PM: (build.command completed in 687ms)
1:53:02 PM: ​
1:53:02 PM: ┌─────────────────────────────┐
1:53:02 PM: │ Netlify Build Complete │
1:53:02 PM: └─────────────────────────────┘
1:53:02 PM: ​
1:53:02 PM: (Netlify Build completed in 706ms)
1:53:02 PM: Caching artifacts
1:53:02 PM: Started saving build plugins
1:53:02 PM: Finished saving build plugins
1:53:02 PM: Started saving pip cache
1:53:02 PM: Finished saving pip cache
1:53:02 PM: Started saving emacs cask dependencies
1:53:02 PM: Finished saving emacs cask dependencies
1:53:02 PM: Started saving maven dependencies
1:53:02 PM: Finished saving maven dependencies
1:53:02 PM: Started saving boot dependencies
1:53:02 PM: Finished saving boot dependencies
1:53:02 PM: Started saving go dependencies
1:53:04 PM: Finished saving go dependencies
1:53:04 PM: Cached ruby version 2.6.2
1:53:04 PM: Build script success
1:53:04 PM: Starting to deploy site from ‘build’
1:53:04 PM: Creating deploy tree
1:53:05 PM: Creating deploy upload records
1:53:05 PM: 0 new files to upload
1:53:05 PM: 0 new functions to upload
1:53:05 PM: Starting post processing
1:53:05 PM: Post processing done
1:53:05 PM: Site is live
1:53:41 PM: Finished processing build request in 1m24.916011782s

Hiya @ReynaldoGonzalez and welcome to our community!

First question for build troubles is always “can you build locally, and are you using the same software versions?” This post has our full build debugging guide:

…which we ask you to read and certify that you’ve checked all the common problems before we dive into helping debug.

Once you’re through that and can share the answers to the last few questions with us (in this thread is preferable since you’ve helpfully laid out all the context here already), we’ll be ready to pick it back up!