Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WEBTHEME not recognizing lcars-picard #1543

Closed
5 tasks done
kenpachizero opened this issue Feb 24, 2024 · 2 comments · Fixed by #1500
Closed
5 tasks done

WEBTHEME not recognizing lcars-picard #1543

kenpachizero opened this issue Feb 24, 2024 · 2 comments · Fixed by #1500

Comments

@kenpachizero
Copy link

kenpachizero commented Feb 24, 2024

Bug,
This is a: Issue with the WEBTHEME environment variable in pihole

Details

Set the WEBTHEME to lcars-picard and i get this error in the logs:

[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[i] Installing /etc/dnsmasq.d/01-pihole.conf...
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[i] Installing /etc/.pihole/advanced/06-rfc6761.conf...
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
[i] Installing latest logrotate script...
[i] Existing logrotate file found. No changes made.
[i] Assigning password defined by Environment Variable
[✓] New password set
[!] Invalid theme name supplied: lcars-picard, falling back to default-light.
[i] Added ENV to php:
"TZ" => "",
"PIHOLE_DOCKER_TAG" => "",
"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
"CORS_HOSTS" => "",
"VIRTUAL_HOST" => "pihole",
[i] Using IPv4 and IPv6
[i] Installing latest Cron script...

How to reproduce the issue

  1. Environment data
  • Operating System: Apline
  • Hardware: Raspberry Pi 4B
  • Kernel Architecture: ArmV8 64bit
  • Docker Install Info and version:
    • Software source: official docker-ce
    • Supplimentary Software: portainer
  • Hardware architecture: ArmV8 64bit
  1. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
    screenshots attached
    2
    3
    1

  2. any additional info to help reproduce

These common fixes didn't work for my issue

  • I have tried removing/destroying my container, and re-creating a new container
  • I have tried fresh volume data by backing up and moving/removing the old volume data
  • I have tried running without my volume data mounts to eliminate volumes as the cause
  • I have checked web/scripts/pi-hole/php/theme.php and can see the line: $available_themes['lcars-picard'] = array('Star Trek Picard LCARS theme (dark)', true, 'lcars-picard', '#53596C');
  • 4

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

@kenpachizero kenpachizero changed the title WEBTHEME not recognazing lcars-picard WEBTHEME not recognizing lcars-picard Feb 24, 2024
@rdwebdesign rdwebdesign linked a pull request Feb 24, 2024 that will close this issue
5 tasks
@PromoFaux
Copy link
Member

Please try again in the latest image - this should now be fixed!

@kenpachizero
Copy link
Author

Yes that did work, Thank you.

truecharts-admin referenced this issue in truecharts/charts Mar 4, 2024
…56 by renovate (#18853)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [pihole/pihole](https://togithub.com/pi-hole/docker-pi-hole) | patch |
`2024.02.0` -> `2024.02.2` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>pi-hole/docker-pi-hole (pihole/pihole)</summary>

###
[`v2024.02.2`](https://togithub.com/pi-hole/docker-pi-hole/releases/tag/2024.02.2)

[Compare
Source](https://togithub.com/pi-hole/docker-pi-hole/compare/2024.02.1...2024.02.2)

Jumped the gun a little with the last tag - didn't realise there were
changes ready to go! Should fix:
[https://github.com/pi-hole/docker-pi-hole/issues/1543](https://togithub.com/pi-hole/docker-pi-hole/issues/1543)

<!-- Release notes generated using configuration in .github/release.yml
at master -->

#### What's Changed

- Enhance theme validation by
[@&#8203;ADawidowski](https://togithub.com/ADawidowski) in
[https://github.com/pi-hole/docker-pi-hole/pull/1500](https://togithub.com/pi-hole/docker-pi-hole/pull/1500)

#### New Contributors

- [@&#8203;ADawidowski](https://togithub.com/ADawidowski) made their
first contribution in
[https://github.com/pi-hole/docker-pi-hole/pull/1500](https://togithub.com/pi-hole/docker-pi-hole/pull/1500)

**Full Changelog**:
pi-hole/docker-pi-hole@2024.02.0...2024.02.2

###
[`v2024.02.1`](https://togithub.com/pi-hole/docker-pi-hole/releases/tag/2024.02.1)

[Compare
Source](https://togithub.com/pi-hole/docker-pi-hole/compare/2024.02.0...2024.02.1)

Nothing Docker-specific this time around, tagging to include FTL v5.25.1

<!-- Release notes generated using configuration in .github/release.yml
at master -->

#### What's Changed (FTL)

- Fix spurious "resource limit exceeded" messages (v5 backport) by
[@&#8203;DL6ER](https://togithub.com/DL6ER) in
[https://github.com/pi-hole/FTL/pull/1893](https://togithub.com/pi-hole/FTL/pull/1893)

**Full Changelog**:
pi-hole/FTL@v5.25...v5.25.1

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 10pm on monday" in timezone
Europe/Amsterdam, Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMjUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjIyNS4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants