enter image description here
Today when using IntelliJ (window) & Spring Boot to create a new project, I started seeing this error:
" Initialization failed for 'https://start.aliyun.com' Please check URL, network and proxy settings
Error Message: Error parsing JSON response "
I tried to modify Setting in IDE, Open --> File -> Settings -> Appearance and Behavior ->System Settings -> HTTP Proxy --> Select Auto-detect proxy settings and set the Automatic proxy configuration URL.
but the problem is still there.
I've just finished creating my custom error messages in my Nuxt.js application in layouts/error.vue. For the moment I've made it pretty simple as it's just a brochure site for the time being, so I am just handling the errors as shown below as for now I only care about users hitting a page that doesn't exist.
<template v-if="error.statusCode === 404">
<h1>Sorry!</h1>
<p>We can't find the page you are looking for.</p>
</template>
<template v-else>
// Some other message
</template>
When running my application locally, and trying to navigate to a route that doesn't exist, this works perfectly and my error message is displayed.
However, my hosted application does not behave how I want it to. I'm hosting the application on IBM Cloud as a Cloud Foundry application. The application uses the static buildpack, and my manifest.yml file looks like so:
---
applications:
- name: name
path: ./dist
buildpack: https://github.com/cloudfoundry/staticfile-buildpack.git
random-route: true
But if I try and navigate to an incorrect route that way, I am displayed the generic nginx 404 error:
I understand that there are 2 ways you can tell Cloud Foundry that the application requires a static buildpack - Declaring the buildpack in the manifest.yml OR adding a file named Staticfile in the dist directory after running npm run generate. Within this file, you can add some configurations, one of which being status codes which:
Allows to define custom pages for HTTP STATUS codes instead of the default NGINX pages.
status_codes:
404: /404.html
500: /500.html
However, my error handling is done in a layout, not a page. And my generated project folder does not contain a page called error anywhere, so I don't know how to use this method to use my error handling.
If anybody could give me some pointers on how to correctly do it, it would be greatly appreciated!
Error Summary
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070003
Config Error Cannot read configuration file
Config File \?\D:\Company\ABC\web.config
Requested URL http://localhost:80/services/application/cardmanagement
Physical Path D:\ABC\DEF\Website.Hosts
Logon Method Not yet determined
Logon User Not yet determined
Config Source
-1:
0:
I am getting this strange error when I try to browse the service. Problem is Physical path is correct but config path is even does not exist in my machine where all applications and iis installed. So I am surprised from where its taking that path and how to correct it.
Lost resource tree under /manager. MODX Revolution 2.2.5-pl (advanced).
Log in to the admin panel is obtained, but the admin is only the top toolbar.
In the core/cache/logs/error.log:
[2013-03-21 11:18:22] (ERROR # /index.php) `` is not a valid integer and may not be passed to makeUrl()
Ie there is no error on the part of a PHP /manager/index.php.
Firebug after login shows:
ReferenceError: _ is not defined
...rer:this.renderNoteCell.createDelegate(this)]});this.grid_panel=new Ext.grid.Gri...
modx.t...tory.js (строка 806)
ReferenceError: _ is not defined
params[this.paramNames.topic] = '/ys/user-' + MODx.user.id + '/';
modx.js (строка 820)
TypeError: MODx.user is undefined
params[this.paramNames.topic] = '/ys/user-' + MODx.user.id + '/';
modx.js (строка 820)
Chrome shows:
Failed to load resource: the server responded with a status of 401 (Not Authorized)
http://example.com/connectors/lang.js.php?
ctx=mgr&topic=topmenu,file,resource,setting,gallery:default&action=70
Uncaught ReferenceError: _ is not defined modx.tree.directory.js:806
Uncaught ReferenceError: _ is not defined modx.localization.js:5
Uncaught TypeError: Cannot read property 'id' of undefined modx.js:820
Error found on this material, all the writing that the matter compress_js and compress_css.
I adjusted the values from 1 to 0 (Table modx_system_settings). Deleted cache. I go to the admin panel - nothing has changed. In the cache now:
core/cache/system_settings/config.cache.php
'compress_css' => '0',
'compress_js' => '0',
Why Chrome is responsible Not Authorized not clear, as if I logged, but MODx does not understand.
I do not understand what the problem is.
You've done an advanced install and moved one or both the manager and core directories?
First, double check all the paths in core/config, the 2 config.core.php in your site root & manager directories, review all this: http://rtfm.modx.com/display/revolution20/Hardening+MODX+Revolution
if you have moved the core out of above the web root, check your php settings & make sure php can read/write to those directories I had to implicitly add the path to the core's parent directory in my php config. [I was getting the same error as you]
Also, js & css compression hasn't been a problem for a while. 2.2.1 I think.
I had almost the same issue. Please double-check all the config files, especially config paths. My task was domain transfering from web to localhost. There are two imoprtant cases - firstly, check paths(especially pay attention on the slashes, under Windows you have different ones, btw you can / and \ at the same times, it depends). Secondly, there are some troubles with suhosin extension but this wasn't my case. Hope it helps.
My Apache log frequently contains message such as "File does not exist". I have a page named 404.shtml and when I try to receive a Invalid page, the contents of 404.shtml are displayed. But at the same time the invalid page url is also written in the logs.
Is is possible avoid such errors within the Apache log, As sometimes the log is flooded with such entries