Config File Config Not Found In

[Chris]

Everything seems to work accordingly if I manually set the config variables instead of importing them. Has anyone encountered anything like this? I wasn't able to find anything helpful in the documentation.

Although this is an old post and very essential problem of Flask, which I happen to have this these days. In case that anyone also have the same problem, you should check the path of config.py file. At first, I created config.py inside app dir. Then I moved outside the app, it works. Like this:

Twil makes good points and alternatives to app.config.from_object. However, I stumbled upon this question while having trouble with the following Flask Tutorial and I wanted to follow the guide and use from_object.

The error message is telling you that whatever configuration got read, it didn't include a top level setting named add. The ConfigFactory.load function will attempt to load the configuration from a variety of places. By default it will look for a file named application with a suffix of .conf or .json. It looks for that file as a Java resource on your class path. However, various system properties will override this default behavior.

Are you using an IDE or sbt? I had a similar problem while using Eclipse. It simply did not find the application.conf file at first and later on failed to notice edits. However, once I ran my program via sbt, all worked just fine, including Eclipse. So, I added 'main/resources' to the libraries (Project -> Properties -> Java Build Path -> Libraries", "add class folder"). That might help you as well.

I ran into this issue inside a Specs2 test that was driven by SBT. It turned out that the issue was caused by In that case, the Thread's contextClassLoader wasn't using the correct classloader. If you run into a similar error, there are other versions of ConfigFactory.load() that allow you to pass the current class's ClassLoader instead. If you're using Specs2 and you're seeing this issue, use a version = 4.0.1.

I suspect I got myself into this pickle by copying an existing project to set up a new project. I had changed library names in dune files but had not renamed my new .opam file. On the other hand, killing ocamlmerlin-server and restarting emacs without fixing that seems to have fixed merlin in both the old and new projects.

Turns out I was editing a file, which was not built by dune. I had a file with same name in my main source tree, and I though I was editing that file, but I had opened the same file under vendored dir, and dune actually never built it, so there was no merlin configuration. Makes sense, shame on me.

I have a user trying to connect via Global Protect from a Win 11 client. The error is "matching client config not found". I have no issues at all connecting as that same user from a Win 10 client. Also we use Mini Orange for MFA which sends an SMS code to the user.

PAN support had me delete the DAT files from c:\users\username\AppData\Local\Palo Alto Networks\GlobalProtect on the Win 11 client. I was able to connect and then upgraded to 5.2.10. After upgrade, I had to again delete those DAT files and then user was able to successfully connect to GP on Win 11.

The error indicates that connecting user does not match any of the user config you have defined. First you need to identify if the error is returned by GP Portal or GP Gateway. You should be able to confirm this from GP logs on the firewall -> Monitor -> GlobalProtect Logs, check at what stage of the VPN connection the error is created.

So the same version of the GP client works fine on Win 10 but not Win 11. Based on your troubleshooting suggestions, it appears the issue lies within the gateway based on what I'm seeing in the GP traffic log. GP client version is 5.2.8-23 on both Win 10 and Win 11 clients.

I opened a case with PAN support. They indicated 5.2.10 and higher is recommended for Win 11. I downloaded 5.2.10 and activated it. After upgrading on a Win 10 client, I'm now getting that same matching client config not found error.

If you said that user is failing to match GP gateway config, this narrow down the problem - because GP gateway agent/client config selection criteria are only based on user, os (and public source ip/region).

What I could imagine (as happened to us) is that Win 11 is using AAD, where user is login with UPN (user principle name), which cause group mapping to fail and the connecting username is not mapped to the user group used in GP gateway config.

I am trying to configure globalprotect to use SAML authentication for the portal and gateway. The authentication seems to work but when, but i am not getting a valid client config when i use groups in allow list.

This seems to be working besides the fact that it tries with 2 different formats. Then the user tries to fetch the config with the same group limitation as the authentication profile this seems to fail. When i remove the group it works and the client can get it's config.

We figured out the issue was with the certificate profile, without client certificate it worked. Normally the domain is taken from the Certificate. For the group mapping you have to specify the NEBTIOS domain name.

Hi Guys,
As i am setting up server in FreeBSD , i installed nextcloud, (downloaded and unzipped) changed all the needed configuration except i do not find the config.php file under config folder in nextcloud. Without which i think i cannot get access to the nextcloud server.

What location/directory is the config.php located in? when I do a locate, I get several config.php files and locations. The documentation just says config/config.php, but does not provide any more on which directory specifically. I am new to server setup for linux. I mostly use Linux as a gui, but am trying to learn more linux command line. I have ubuntu server setup.

I took a look at that wiki and when going to /var/snap/nextcloud/current/ the config file is completely empty.
And when trying to access /var/snap/nextcloud/common/nextcloud it says permission denied.

As far as I tracked down this issue it is important that the names used for rightid and leftid are also on the SAN of the certificates (see VPN server using StrongSwan "no matching peer config found" - what does it mean?). Which in my opinion is the case:

The strange thing is that this configuration file does exist, and the path is correct, but I don't understand why that error message appears. Please, could you help me to identify what is the problem that I am having?

Logstash can load multiple files with the *.conf extension from a configuration DIRECTORY. Try starting it with the path to the directory/folder with the configuration file(s). As long as the file ends with .conf, Logstash should see it and load it.

This feature also means that if you should ever want to disable a config file, you do not need to delete it. All you need to do is to rename it so it no longer ends in .conf. Add a .disabled is the standard I think.

Okay. I stand corrected. But there is something about file extensions being relevant for Logstash modules? Or is that Filebeat modules? Something about the modules being shipped out-of-the-box with a .disabled extension, and enabling them (either with a little enable tool, or manually) just involves deleting or adding the .disabled extension?

As I said, if you point path.config at a directory then it will read everything in the directory. If I point path.config to a /tmp/conf.d directory that contains two files, one a valid configuration and the other a few megabytes of /dev/random then logstash will complain

[2023-03-18T14:54:24,069][DEBUG][logstash.config.source.local.configpathloader] Skipping the following files while reading config since they don't match the specified glob pattern :files=>["/tmp/conf.d/zzz.disabled"]
[2023-03-18T14:54:24,071][DEBUG][logstash.config.source.local.configpathloader] Reading config file :config_file=>"/tmp/conf.d/test.conf"

It is recommended to define the configuration in a dedicated JavaScript, TypeScript or JSON file. The file will be discovered automatically, if it is named jest.config.jstsmjscjsjson. You can use --config flag to pass an explicit path to the file.

By default, Jest runs all tests and produces all errors into the console upon completion. The bail config option can be used here to have Jest stop running tests after n failures. Setting bail to true is the same as setting bail to 1.

Jest attempts to scan your dependency tree once (up-front) and cache it in order to ease some of the filesystem churn that needs to happen while running tests. This config option lets you customize where Jest stores that cache data on disk.

Automatically clear mock calls, instances, contexts and results before every test. Equivalent to calling jest.clearAllMocks() before each test. This does not remove any mock implementation that may have been provided.

Indicates whether the coverage information should be collected while executing the test. Because this retrofits all executed files with coverage collection statements, it may significantly slow down your tests.

The babel and v8 coverage providers use /* istanbul ignore next */ and /* c8 ignore next */ comments to exclude lines from coverage reports, respectively. For more information, you can view the istanbuljs documentation and the c8 documentation.

An array of glob patterns indicating a set of files for which coverage information should be collected. If a file matches the specified glob pattern, coverage information will be collected for it even if no tests exist for this file and it's never required in the test suite.