Subpage not working after Digital Ocean Deployment

http://iconcodex.com/icons
Guys i need your help. lost 3 days with this and i am … lost now
On local machine when i click a category works fine / on server (digital ocean ubuntu-apache php7) does not work. I need some help. If i click a Icon Set - gives me a 404.

.htaccess is present and i have

RewriteEngine on
RewriteBase /

i tried:

<Directory /var/www/>
        Options Indexes FollowSymLinks
        AllowOverride All
        Require all granted
</Directory>

my .htaccess is not ignored.

this is how i list the icons in /icons/category_name:

template:

        <?php foreach ($page->files() as $img): ?>
        <li class="icn-box">
            <span class="icname"><?php echo $img->iconname() ?></span>            
            <span class="icntype"><?php echo $img->extension() ?></span>
            <span class="icnsize"><?php echo $img->niceSize() ?></span>
            <span class="icndate"><?php echo $img->modified('d M Y') ?></span>
            <span class="icn-width"><?php echo $img->width() ?></span>
            <span class="icn-height"><?php echo $img->height() ?></span>
            <span class="icontags"><?php echo $img->icontags() ?></span>
            <span class="hidden">Drag & Drop like a King.</span>
            <img src="<?= $img->url() ?>" alt="<?= $img->title() ?>">  
            <?= '<div id="svgcode"><xmp>' . file_get_contents($img->url()) . '  </xmp></div>';?>          
        </li>        
        <?php endforeach ?>
    </ul>

Rewriting doesn’t work, is it enabled on the server?

sudo a2enmod rewrite

Module rewrite already enabled

And the same result if you don’t set the RewriteBase?

yes. please find a solution with me cause i am breaking up.

this is how it looks on my local dev env.

How have you made sure the .htaccess is actually not ignored?

i wrote couple of characters. the website didn’t load.

Hm, subpages in general seem to be working, it seems(the icons page itself, resources etc), but not those links. What’s your content structure like? But the strange thing is that it comes up with the server error page and not Kirby’s error page.

1 Like

i got this in apache logs:

AH01276: Cannot serve directory /usr/share/apache2/icons/: No matching DirectoryIndex (index.php,index.pl,index.cgi,index.html,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive
# Kirby .htaccess

# rewrite rules
<IfModule mod_rewrite.c>

# enable awesome urls. i.e.:
# http://yourdomain.com/about-us/team
RewriteEngine on

# make sure to set the RewriteBase correctly
# if you are running the site in a subfolder.
# Otherwise links or the entire site will break.
#
# If your homepage is http://yourdomain.com/mysite
# Set the RewriteBase to:
#
# RewriteBase /mysite

# In some environments it's necessary to
# set the RewriteBase to:
#
RewriteBase /

# block files and folders beginning with a dot, such as .git
# except for the .well-known folder, which is used for Let's Encrypt and security.txt
RewriteRule (^|/)\.(?!well-known\/) index.php [L]

# block text files in the content folder from being accessed directly
RewriteRule ^content/(.*)\.(txt|md|mdown)$ index.php [L]

# block all files in the site folder from being accessed directly
# except for requests to plugin assets files
RewriteRule ^site/(.*) index.php [L]

# Enable authentication header
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

# block direct access to kirby and the panel sources
RewriteRule ^kirby/(.*) index.php [L]

# make site links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php [L]

</IfModule>

# compress text file responses
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
</IfModule>
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride All
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/html>
	Options Indexes FollowSymLinks
	AllowOverride All
	Require all granted
</Directory>


#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

The error log entry is probably caused by me trying to access /icons/, so that’s not really important.

Are these page actually readable by the webserver?

As I said above, the really strange this is that rewriting seems to work, otherwise images wouldn’t work nor the other first level pages.

But something is getting in the way and I have no idea what and why the error is handled by the server and not through Kirby’s router. Is there any other stuff on the server that might interfere?

Could you also please post the contents of your /site/templates folder and your complete template code for the single icons page.

folder

<?php snippet('header') ?>

<?php snippet('lsidebar') ?>


<div class="icon-gallery-box boxme-content">
<?php snippet('search') ?>
    <ul class="icon-gallery">
        <?php foreach ($page->files() as $img): ?>
        <li class="icn-box">
            <span class="icname"><?php echo $img->iconname() ?></span>            
            <span class="icntype"><?php echo $img->extension() ?></span>
            <span class="icnsize"><?php echo $img->niceSize() ?></span>
            <span class="icndate"><?php echo $img->modified('d M Y') ?></span>
            <span class="icn-width"><?php echo $img->width() ?></span>
            <span class="icn-height"><?php echo $img->height() ?></span>
            <span class="icontags"><?php echo $img->icontags() ?></span>
            <span class="hidden">Drag & Drop like a King.</span>
            <img src="<?= $img->url() ?>" alt="<?= $img->title() ?>">  
            <?= '<div id="svgcode"><xmp>' . file_get_contents($img->url()) . '  </xmp></div>';?>          
        </li>
        
        <?php endforeach ?>
    </ul>
    <div class="author">
        <div class="author-container">Designed and Built by <span><a target="_blank" rel="noopener noreferrer" href="https://twitter.com/madebyoliver">Oliver</a></span></div>
    </div>   
</div>

<?php snippet('rsidebar') ?>
<?php snippet('footer') ?>

Please remember that on local machine works like a charm. It’s something with that environment. Should i change the host, i am willing to do anything to see it live as it’s on my machine.

The Panel seems to be available. Can you actually log in and access those subpages in the Panel?

It shouldn’t be necessary to change providers. Just a matter of finding out what the problem is.

Yes. i can access the subpages in panel but not the files.
i have an error accessing the files:

Call to undefined function Kirby\Image\simplexml_load_string()

I installed

sudo apt-get install php-xml

restarted the apache, same result on frontend, backend now allows me to access files.