[GH-ISSUE #821] [BUG] 405 Method not allowed

kerem commented

2026-02-25 20:35:56 +03:00

Owner

Originally created by @sutidor on GitHub (Jul 27, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/821

Describe the bug
When I enter any term in the address bar for the first time: 405 Method not allowed
When I enter this term or any other term AGAIN to the same address bar DIRECTLY AFTER, it will search normally.

Since I could not find any1 else with this issue I presume there is an issue in my config but it only happened in versions 0.7 onward (currently 0.7.4). Using firefox and reinstalled the search engine with current version. Behind nginx reverse proxy. Happens on smartphone, too.

To Reproduce
Steps to reproduce the behavior:

Go to address bar
search anything (405 Method not allowed)
search again
searches normally

Deployment Method

Heroku (one-click deploy)
Docker
run executable
pip/pipx
Other: [describe setup]

Version of Whoogle Search

Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
Version [version number]
Not sure

Desktop (please complete the following information):

OS: Win11
Browser Firefox
Version 102

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Originally created by @sutidor on GitHub (Jul 27, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/821 **Describe the bug** When I enter any term in the address bar for the first time: 405 Method not allowed When I enter this term or any other term AGAIN to the same address bar DIRECTLY AFTER, it will search normally. Since I could not find any1 else with this issue I presume there is an issue in my config but it only happened in versions 0.7 onward (currently 0.7.4). Using firefox and reinstalled the search engine with current version. Behind nginx reverse proxy. Happens on smartphone, too. **To Reproduce** Steps to reproduce the behavior: 1. Go to address bar 2. search anything (405 Method not allowed) 3. search again 4. searches normally **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [x] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ ] Not sure **Desktop (please complete the following information):** - OS: Win11 - Browser Firefox - Version 102 **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Add any other context about the problem here.

kerem

2026-02-25 20:35:56 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:35:56 +03:00

Author

Owner

@tootbrute commented on GitHub (Jul 28, 2022):

Just chiming in to say that I have this same problem but only on some of my machines. Information below.

Deployment Method
--> Docker
(running on Yunohost behind NGINX)

Version of Whoogle Search
--> Version 0.7.4

Desktop:

--> OS: Fedora 36 (no problems!)
Browser Firefox
Version 102

--> OS: Ubuntu 22
Browser: Firefox (get this 405 error)
Version: 103

--> OS: Ubuntu 22 (same system as above)
Browser: Brave (no 405 error, but doesn't complete search, just shows a blank Whoogle page)
Version: 1.41.100 Chromium: 103.0.5060.134 (Official build) (64-bit)

Smartphone (please complete the following information):

--> Device: Asus Zenfone Pro Max 2
OS: LineageOS 18.1
Browser Firefox (Currently can't add Whoogle search to Firefox "error connecting to Whoogle")
Version 102.2.1

(same device as above) - works!
Browser: Bromite
Version 103.0.5060.140

@tootbrute commented on GitHub (Jul 28, 2022): Just chiming in to say that I have this same problem but only on some of my machines. Information below. Deployment Method --> Docker (running on Yunohost behind NGINX) Version of Whoogle Search --> Version 0.7.4 Desktop: --> OS: Fedora 36 (no problems!) Browser Firefox Version 102 --> OS: Ubuntu 22 Browser: Firefox (get this 405 error) Version: 103 --> OS: Ubuntu 22 (same system as above) Browser: Brave (no 405 error, but doesn't complete search, just shows a blank Whoogle page) Version: 1.41.100 Chromium: 103.0.5060.134 (Official build) (64-bit) Smartphone (please complete the following information): --> Device: Asus Zenfone Pro Max 2 OS: LineageOS 18.1 Browser Firefox (Currently can't add Whoogle search to Firefox "error connecting to Whoogle") Version 102.2.1 (same device as above) - works! Browser: Bromite Version 103.0.5060.140

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@erikderzweite commented on GitHub (Jul 31, 2022):

Deployment Method
--> Docker
(running on Yunohost behind NGINX)

Version of Whoogle Search
--> Version 0.7.4

--> OS: Ubuntu 18
Browser: Firefox (405 error second search works fine, after a longer pause 405 again)
Version: 103

--> OS: Ubuntu 18
Browser: Chromium (no 405, just whoogle landing page after putting a search term in address bar, second search works)
Version: 103.0.5060.134 snap

@erikderzweite commented on GitHub (Jul 31, 2022): Deployment Method --> Docker (running on Yunohost behind NGINX) Version of Whoogle Search --> Version 0.7.4 --> OS: Ubuntu 18 Browser: Firefox (405 error second search works fine, after a longer pause 405 again) Version: 103 --> OS: Ubuntu 18 Browser: Chromium (no 405, just whoogle landing page after putting a search term in address bar, second search works) Version: 103.0.5060.134 snap

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@benbusby commented on GitHub (Aug 1, 2022):

@sutidor (or anyone else with this issue) can you give me a breakdown of the full request details sent to Whoogle when the 405 code is returned (i.e. which endpoint, what request type (POST vs GET), etc)? I'm wondering if there's an opensearch caching issue here. I haven't been able to reproduce on my end, so I'll have to debug this a bit blind.

@benbusby commented on GitHub (Aug 1, 2022): @sutidor (or anyone else with this issue) can you give me a breakdown of the full request details sent to Whoogle when the 405 code is returned (i.e. which endpoint, what request type (POST vs GET), etc)? I'm wondering if there's an opensearch caching issue here. I haven't been able to reproduce on my end, so I'll have to debug this a bit blind.

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@sutidor commented on GitHub (Aug 1, 2022):

@benbusby from the opensearch.xml I assume it is a POST request. Additional context sent to the email provided in your github (contact@) Thank you
Edit: Autocomplete works by the way.

@sutidor commented on GitHub (Aug 1, 2022): @benbusby from the opensearch.xml I assume it is a POST request. Additional context sent to the email provided in your github (contact@) Thank you Edit: Autocomplete works by the way.

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@benbusby commented on GitHub (Aug 2, 2022):

@sutidor could you (or anyone here) try out the latest changes on main or the latest Docker tag (once it's finished building -- should be out in the next ~15-30 mins)? I just pushed a fix for a different issue that I think might fix this issue as well, hopefully.

@benbusby commented on GitHub (Aug 2, 2022): @sutidor could you (or anyone here) try out the latest changes on `main` or the `latest` Docker tag (once it's finished building -- should be out in the next ~15-30 mins)? I just pushed a fix for a different issue that I think might fix this issue as well, hopefully.

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@tootbrute commented on GitHub (Aug 3, 2022):

@sutidor could you (or anyone here) try out the latest changes on main or the latest Docker tag (once it's finished building -- should be out in the next ~15-30 mins)? I just pushed a fix for a different issue that I think might fix this issue as well, hopefully.

On Fedora, Firefox and Brave is now working for me using the latest image.

$ sudo docker images
REPOSITORY                     TAG       IMAGE ID       CREATED         SIZE
benbusby/whoogle-search        latest    31b9b63a5770   10 hours ago    108MB

@tootbrute commented on GitHub (Aug 3, 2022): > @sutidor could you (or anyone here) try out the latest changes on `main` or the `latest` Docker tag (once it's finished building -- should be out in the next ~15-30 mins)? I just pushed a fix for a different issue that I think might fix this issue as well, hopefully. On Fedora, Firefox and Brave is now working for me using the latest image. ``` $ sudo docker images REPOSITORY TAG IMAGE ID CREATED SIZE benbusby/whoogle-search latest 31b9b63a5770 10 hours ago 108MB ```

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@benbusby commented on GitHub (Aug 4, 2022):

Thanks for clarifying. I'm going to assume this is fixed for everyone, but anyone can feel free to re-open if that's not the case for them.

@benbusby commented on GitHub (Aug 4, 2022): Thanks for clarifying. I'm going to assume this is fixed for everyone, but anyone can feel free to re-open if that's not the case for them.

kerem commented

2026-02-25 20:35:57 +03:00

Author

Owner

@selenias commented on GitHub (Aug 12, 2022):

@benbusby: i have the same issue as the users above. From time to time i get a white page with "Method Not Allowed" (The method is not allowed for the requested URL.). This happens a few times a day. Just now i started a Firefox Private Window.

few weeks ago, i installed whoogle for the first time to try it out. at that point i had a rather simple setup in docker (unfortunately i don't have the YML anymore). And i was accessing it via IP address. I added it to firefox so i could search via the address bar. for a few weeks that worked, so yesterday i decided to clean install the container. Since then i got the 405 error.

I don't know for sure but i think i was running 0.7.4, two weeks ago (it was a test so i flung it together quickly). yesterday i was running the latest version from i think august 10th (can't be sure, i know the Digest ID's are different now). Today i updated it again to the latest version (aug 11th, 6:40PM) and i still have the issue.

the differences between the last couple of weeks and yesterday/today are several (in my case).

added networks to docker
created specific volume names (i wanted to bind mount it on the local host but was unable to make it work)
changed the port from which i access it (http://host:port)
added some environment variables preloaded (So i wouldn't have to set this via the website configuration).
access it via domain name https://whoogle.mydomain.com (reverse proxy via Traefik).

Here is my YML file

---
version: '3.8'

networks:
  proxy-internal:
    # use a pre-existing network
    external: true


volumes:
  workdir:
  confdir:


services:

# can't use mem_limit in a 3.x docker-compose file in non swarm mode
# see https://github.com/docker/compose/issues/4513

  whoogle-search:
    container_name: whoogle
    image: benbusby/whoogle-search:latest
    networks:
     - proxy-internal

    # Restart policy UNLESS-STOPPED (better choice) | ON-FAILURE | ALWAYS | NO
    restart: unless-stopped


    security_opt:                                           # Prevents your container processes from gaining additional privileges
      - no-new-privileges:true                              # NOTE: no spaces between ':' and 'TRUE'


    logging:                                                # Log settings, max 5 files of 1MB size.
      driver: json-file
      options:
        max-file: 5
        max-size: 1M

    ports:
      - 5000:5000                           # Custom port

    volumes:
      - /etc/localtime:/etc/localtime:ro                    # Sync time
      - workdir:/whoogle                                       # Directory to store WORKDIR (not entirely sure if this matters)
      - confdir:/config                                            # Directory to store the configuration (i.e. darkmode)


    environment:
#      WHOOGLE_URL_PREFIX:                           # The URL prefix to use for the whoogle instance (i.e. "/whoogle")
      WHOOGLE_AUTOCOMPLETE: on                      # Controls visibility of autocomplete/search suggestions. Default on -- use '0' to disable.
      WHOOGLE_RESULTS_PER_PAGE: 20                  # Set the number of results per page

      # Config Environment Variables (the browser config)
      WHOOGLE_CONFIG_COUNTRY: US                    # Filter results by hosting country
      WHOOGLE_CONFIG_LANGUAGE: lang_en              # Set interface language
      WHOOGLE_CONFIG_THEME: dark                    # Set theme mode (light, dark, or system)
      WHOOGLE_CONFIG_TOR: off                       # Use Tor routing (if available)
#      WHOOGLE_CONFIG_URL: http://address/           # The root url of the instance (https://<your url>/) (NOTE: seems you don't need to set this with traefik)

@selenias commented on GitHub (Aug 12, 2022): @benbusby: i have the same issue as the users above. From time to time i get a white page with "Method Not Allowed" (The method is not allowed for the requested URL.). This happens a few times a day. Just now i started a Firefox Private Window. few weeks ago, i installed whoogle for the first time to try it out. at that point i had a rather simple setup in docker (unfortunately i don't have the YML anymore). And i was accessing it via IP address. I added it to firefox so i could search via the address bar. for a few weeks that worked, so yesterday i decided to clean install the container. Since then i got the 405 error. I don't know for sure but i think i was running 0.7.4, two weeks ago (it was a test so i flung it together quickly). yesterday i was running the latest version from i think august 10th (can't be sure, i know the Digest ID's are different now). Today i updated it again to the latest version (aug 11th, 6:40PM) and i still have the issue. the differences between the last couple of weeks and yesterday/today are several (in my case). 1) added networks to docker 2) created specific volume names (i wanted to bind mount it on the local host but was unable to make it work) 3) changed the port from which i access it (http://host:port) 4) added some environment variables preloaded (So i wouldn't have to set this via the website configuration). 5) access it via domain name https://whoogle.mydomain.com (reverse proxy via Traefik). Here is my YML file ``` --- version: '3.8' networks: proxy-internal: # use a pre-existing network external: true volumes: workdir: confdir: services: # can't use mem_limit in a 3.x docker-compose file in non swarm mode # see https://github.com/docker/compose/issues/4513 whoogle-search: container_name: whoogle image: benbusby/whoogle-search:latest networks: - proxy-internal # Restart policy UNLESS-STOPPED (better choice) | ON-FAILURE | ALWAYS | NO restart: unless-stopped security_opt: # Prevents your container processes from gaining additional privileges - no-new-privileges:true # NOTE: no spaces between ':' and 'TRUE' logging: # Log settings, max 5 files of 1MB size. driver: json-file options: max-file: 5 max-size: 1M ports: - 5000:5000 # Custom port volumes: - /etc/localtime:/etc/localtime:ro # Sync time - workdir:/whoogle # Directory to store WORKDIR (not entirely sure if this matters) - confdir:/config # Directory to store the configuration (i.e. darkmode) environment: # WHOOGLE_URL_PREFIX: # The URL prefix to use for the whoogle instance (i.e. "/whoogle") WHOOGLE_AUTOCOMPLETE: on # Controls visibility of autocomplete/search suggestions. Default on -- use '0' to disable. WHOOGLE_RESULTS_PER_PAGE: 20 # Set the number of results per page # Config Environment Variables (the browser config) WHOOGLE_CONFIG_COUNTRY: US # Filter results by hosting country WHOOGLE_CONFIG_LANGUAGE: lang_en # Set interface language WHOOGLE_CONFIG_THEME: dark # Set theme mode (light, dark, or system) WHOOGLE_CONFIG_TOR: off # Use Tor routing (if available) # WHOOGLE_CONFIG_URL: http://address/ # The root url of the instance (https://<your url>/) (NOTE: seems you don't need to set this with traefik) ```

Rows
Columns

[GH-ISSUE #821] [BUG] 405 Method not allowed #515