Hm, strange. What happens if you place a symbolic link into /etc/apache2/conf-enabled and restart apache:

Regarding the "ERROR: Module weatherradio does not exist!" error, I had the same problem but, since the file has a ".conf" extension, I used the command "sudo a2enconf weatherradio" and things got working.

Hope this helps.

I did it already but no effect:
looks like this:
wxr-xr-x 2 root root 4096 Nov 24 17:43 .
drwxr-xr-x 8 root root 4096 Nov 24 19:27 ..
lrwxrwxrwx 1 root root 30 Mär 12 2020 charset.conf -> ../conf-available/charset.conf
lrwxrwxrwx 1 root root 44 Mär 12 2020 localized-error-pages.conf -> ../conf-available/localized-error-pages.conf
lrwxrwxrwx 1 root root 46 Mär 12 2020 other-vhosts-access-log.conf -> ../conf-available/other-vhosts-access-log.conf
lrwxrwxrwx 1 root root 31 Mär 12 2020 security.conf -> ../conf-available/security.conf
lrwxrwxrwx 1 root root 36 Mär 12 2020 serve-cgi-bin.conf -> ../conf-available/serve-cgi-bin.conf
lrwxrwxrwx 1 root root 35 Nov 24 17:43 weatherradio.conf -> ../conf-available/weatherradio.conf

now the restart apache service:

no error, but access to the webpage.

pi@allsky:/etc/apache2/conf-enabled $ sudo systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-11-24 19:30:20 CET; 2min 24s ago
Docs: httpd.apache.org/docs/2.4/
Process: 5221 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
Main PID: 5225 (apache2)
Tasks: 55 (limit: 4915)
CGroup: /system.slice/apache2.service
├─5225 /usr/sbin/apache2 -k start
├─5226 /usr/sbin/apache2 -k start
└─5227 /usr/sbin/apache2 -k start

Nov 24 19:30:20 allsky systemd[1]: Starting The Apache HTTP Server...
Nov 24 19:30:20 allsky apachectl[5221]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1.
Nov 24 19:30:20 allsky systemd[1]: Started The Apache HTTP Server.

mods-enabled:

pi@allsky:/etc/apache2/mods-enabled $ ll
insgesamt 8
drwxr-xr-x 2 root root 4096 Mär 12 2020 .
drwxr-xr-x 8 root root 4096 Nov 24 19:27 ..
lrwxrwxrwx 1 root root 36 Mär 12 2020 access_compat.load -> ../mods-available/access_compat.load
lrwxrwxrwx 1 root root 28 Mär 12 2020 alias.conf -> ../mods-available/alias.conf
lrwxrwxrwx 1 root root 28 Mär 12 2020 alias.load -> ../mods-available/alias.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 auth_basic.load -> ../mods-available/auth_basic.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 authn_core.load -> ../mods-available/authn_core.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 authn_file.load -> ../mods-available/authn_file.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 authz_core.load -> ../mods-available/authz_core.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 authz_host.load -> ../mods-available/authz_host.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 authz_user.load -> ../mods-available/authz_user.load
lrwxrwxrwx 1 root root 32 Mär 12 2020 autoindex.conf -> ../mods-available/autoindex.conf
lrwxrwxrwx 1 root root 32 Mär 12 2020 autoindex.load -> ../mods-available/autoindex.load
lrwxrwxrwx 1 root root 30 Mär 12 2020 deflate.conf -> ../mods-available/deflate.conf
lrwxrwxrwx 1 root root 30 Mär 12 2020 deflate.load -> ../mods-available/deflate.load
lrwxrwxrwx 1 root root 26 Mär 12 2020 dir.conf -> ../mods-available/dir.conf
lrwxrwxrwx 1 root root 26 Mär 12 2020 dir.load -> ../mods-available/dir.load
lrwxrwxrwx 1 root root 26 Mär 12 2020 env.load -> ../mods-available/env.load
lrwxrwxrwx 1 root root 29 Mär 12 2020 filter.load -> ../mods-available/filter.load
lrwxrwxrwx 1 root root 27 Mär 12 2020 mime.conf -> ../mods-available/mime.conf
lrwxrwxrwx 1 root root 27 Mär 12 2020 mime.load -> ../mods-available/mime.load
lrwxrwxrwx 1 root root 32 Mär 12 2020 mpm_event.conf -> ../mods-available/mpm_event.conf
lrwxrwxrwx 1 root root 32 Mär 12 2020 mpm_event.load -> ../mods-available/mpm_event.load
lrwxrwxrwx 1 root root 34 Mär 12 2020 negotiation.conf -> ../mods-available/negotiation.conf
lrwxrwxrwx 1 root root 34 Mär 12 2020 negotiation.load -> ../mods-available/negotiation.load
lrwxrwxrwx 1 root root 33 Mär 12 2020 reqtimeout.conf -> ../mods-available/reqtimeout.conf
lrwxrwxrwx 1 root root 33 Mär 12 2020 reqtimeout.load -> ../mods-available/reqtimeout.load
lrwxrwxrwx 1 root root 31 Mär 12 2020 setenvif.conf -> ../mods-available/setenvif.conf
lrwxrwxrwx 1 root root 31 Mär 12 2020 setenvif.load -> ../mods-available/setenvif.load
lrwxrwxrwx 1 root root 29 Mär 12 2020 status.conf -> ../mods-available/status.conf
lrwxrwxrwx 1 root root 29 Mär 12 2020 status.load -> ../mods-available/status.load

Hi,

what you write is exactly what the docs are saying, but this doesn’t work. Do you mean eventually I should use:

Sudo a2enmod Weatherradio.conf ?

Hi again,

sudo a2enconf weatherradio
Conf weatherradio already enabled

done, I had to delete the manual symlink and did the a2enconf ..

sudo rm weatherradio.conf
pi@allsky:/etc/apache2/conf-enabled $ sudo a2enconf weatherradio
Enabling conf weatherradio.
To activate the new configuration, you need to run:
systemctl reload apache2
pi@allsky:/etc/apache2/conf-enabled $ systemctl reload apache2

Perfectly right, the documentation is wrong. It needs to beI corrected it in the current version.

done,

thanks a lot

In case anyone else has tried allsky on the pi you are running weatherradio on you may find that weatherradio suddenly stops serving webpages

One workaround is;
Ensure apache is running.

sudo systemclt status apache2

If you installed allsky it will install lighttpd and that will grab port 80 so apache can't run unless you change the port it listens to to something other than 80.

I changed it to port 81

Then you would access weather radio as

http://weather radio:81/weatherradio

A better solution would be to get weatherradio to run on lighttpd or to get allsky to run on apache

hello
I have a small problem with WeatherRadio, not serious but recurring.
I don't know for what but each time, after a certain time I have the weather crashing.
So I have to restart the serverindi of the weather, it can take a week or sometimes less or more.
Who has an idea of where the problem can come from.
I have version 1.8

Hm, strange, haven't seen that in my setup. Mine is running for weeks without a problem.

Do you have a log file available?

Absolutely. If there is somebody out there having a config file for lighthttpd, it would be great to share it. Then I could include it into the next release.

Btw, it should not be that complicated, since it simply serves some files.