• I read countless articles about this error message and potential ways to solve this. Nothing helped me. I could need help to figure to what the problem might be.

    My situation:

    I have a nginx installation on my debian server. I configured a general nginx.conf (http settings) and I have a list of sites-enabled. My nginx does basically the https termination for a couple of applications on my server. Now I installed wordpress in a docker environment.

    I used the following docker compose file.

    version: "3.9"

    services:
    db:
    image: mysql:8.0
    container_name: db_wp
    restart: always
    environment:
    - MYSQL_DATABASE=wordpress
    - MYSQL_ROOT_PASSWORD=<MYPASSWORD>
    - MYSQL_USER=wordpress
    - MYSQL_PASSWORD=<ANOTHER_PASSWORD>
    volumes:
    - /opt/docker/instances/wordpress/dbdata:/var/lib/mysql

    wordpress:
    depends_on:
    - db
    image: wordpress:latest
    container_name: wordpress
    ports:
    - 127.0.0.1:9000:80
    restart: always
    environment:
    - WORDPRESS_DB_HOST=db:3306
    - WORDPRESS_DB_USER=wordpress
    - WORDPRESS_DB_PASSWORD=wordpress
    - WORDPRESS_DB_NAME=wordpress
    volumes:
    - /opt/docker/instances/wordpress/data:/var/www/html

    volumes:
    db_data: {}

    I configured Nginx to forward https to http//localhost:9000.

    After completed startup I went to the server name where wordpress should be reachable, the installation screen came up asking for my language and I let the installation complete.

    After that I had to login and was brought to the wp-admin page. Everything exactly as it should be.

    Then I went to the themes config section, clicked on “Add new Theme” and I got his message:

    An unexpected error occurred. Something may be wrong with www.ads-software.com or this server’s configuration. If you continue to have problems, please try the support forums.

    The same as many posts complained about.

    What did I checkout so far?

    I went to the plugin config section and clicked on Add new Plugin. It worked. No Problems at all

    By default, 3 Themes were provided after the installation. Instead of trying to install a new one I clicked on update on one of them. After a short while it said: Update succesfull

    I went into the docker container (docker exec …..) of wordpress and did a network test with curl to api.www.ads-software.com. It is reachable

    Everything seems to work perfectly but I still get this error for adding a new theme.

    I also added a WP_DEBUG to my config but no debug is produced:

    define( ‘WP_DEBUG’, true );

    define( ‘WP_DEBUG_LOG’, ‘/var/www/html/logs/problems.log’) ;

    No log is written.

    Any ideas what could be my problem ? (I doubt that my problem is nginx related so I did not provide its config here)

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hello @magicroomy,

    You might find the WordPress Playground helpful in troubleshooting this issue, as it encounters a similar problem when accessing the www.ads-software.com plugin or theme directory. There is a related issue discussed on GitHub that outlines potential solutions for this problem.

    You can check out the details and suggested solutions in the GitHub issue for WordPress Playground. This might give you insights into resolving the error with the theme directory/network access in your Docker-based setup.

    Do you possibly have a firewall actively controlling the outgoing connection from nginx? Then curl would also be of little help for testing.

    Also have a look under Tools > Site Health to see what other messages are available there.

    Thread Starter magicroomy

    (@magicroomy)

    Well, if there was a firewall problem: Why does the handling of the plugins work? They also surely require network connections ? Also updating a theme worked .

    The Health check “complains” about some things I would regard not to be related:

    • “Your site is set to display errors to site visitors” => Sure, since I activated the debug log. No worries here
    • “You should remove inactive plugins” AND “You should remove inactive themes”. I could do but I doubt it is my problem.
    • “Page cache is not detected but the server response time is OK”. Also not something I would relate to outgoing netwark connections.

    • This reply was modified 3 days, 3 hours ago by magicroomy.
    • This reply was modified 3 days, 3 hours ago by magicroomy.

    The message displayed in the themes only appears if the http request has failed. Install this plugin: https://www.ads-software.com/plugins/http-requests-manager/ – after the installation you then execute the action where the error occurs. Then go to Tools > HTTP Requests Manager. There you should then be able to see the request to the WordPress API and its response. This may provide further clues as to the cause.

    Thread Starter magicroomy

    (@magicroomy)

    It gets even stranger. I installed the Request manager. It does not show any error. Every Call is answered by wordpress org with a 200 response code. It just seems that the list of available themes is empty.

    As a next step I tried again to click on “Add new Theme”. Same error as above of course.

    Then I pressed the “Back” button in my browser and clicked the “Add new Theme” Button again. Hossa: it worked. All themes appeared.

    It’s great that it works. Does it also work if you deactivate the Request Manager plugin? Not that this is a side effect of it (which I would find strange).

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.