I updated npm on my DigitalOcean droplet, now the axios post call in my authentication (log in) function isn't working. I added a console.log and know that the function is triggered, but the axios post request is not working on the live site. The axios post request still works on my localhost.
I'm getting this error code on the live site:
POST https://www.myexamplesite.com/auth/login 504 (Gateway Time-out) - xhr.js:175
(anonymous) # 2.d105a7aa.chunk.js:1
e.exports # 2.d105a7aa.chunk.js:1
e.exports # 2.d105a7aa.chunk.js:1
Promise.then (async)
u.request # 2.d105a7aa.chunk.js:1
r.forEach.u.<computed> # 2.d105a7aa.chunk.js:1
(anonymous) # 2.d105a7aa.chunk.js:1
onClick # main.84d90956.chunk.js:1
l # 2.d105a7aa.chunk.js:1
d # 2.d105a7aa.chunk.js:1
(anonymous) # 2.d105a7aa.chunk.js:1
m # 2.d105a7aa.chunk.js:1
at # 2.d105a7aa.chunk.js:1
ot # 2.d105a7aa.chunk.js:1
lt # 2.d105a7aa.chunk.js:1
dt # 2.d105a7aa.chunk.js:1
D # 2.d105a7aa.chunk.js:1
F # 2.d105a7aa.chunk.js:1
Xt # 2.d105a7aa.chunk.js:1
Zt # 2.d105a7aa.chunk.js:1
t.unstable_runWithPriority # 2.d105a7aa.chunk.js:1
Ho # 2.d105a7aa.chunk.js:1
M # 2.d105a7aa.chunk.js:1
Gt # 2.d105a7aa.chunk.js:1
Again, the axios post request works fine on the localhost. But the live site sends this error since updating npm (I think it was npm that I updated; there's a chance it was something else). Also, every once and a while I think I've gotten an error about something wrong with a Promise. But that error hasn't appeared for a while.
Any thoughts on how to fix this?
The issue with the new update was that it would no longer allow self certification. I had to add this to the server:
process.env.NODE_TLS_REJECT_UNAUTHORIZED='0';
That is a temporary fix until I'm able to get the website certification working properly. I still think there may be an issue with the new npm update because I didn't self-certify my site, I used an official certification system. Don't know why this error happened. Still trying to figure out how to make the app work again without the process.env.NODE_TLS_REJECT_UNAUTHORIZED='0'; in the server.
Related
How do you locate where in a HTML page Javascript initially calls a jQuery event?
I'm attempting to diagnose and track down an obnoxious Datatables bug that has this traceback:
datatables.min.js:50 Uncaught TypeError: Cannot set properties of undefined (setting '_DT_CellIndex')
at fb (datatables.min.js:50:21)
at ia (datatables.min.js:45:1)
at HTMLTableRowElement.<anonymous> (datatables.min.js:45:114)
at jquery-3.5.1.min.js:2:1540
at Function.map (jquery-3.5.1.min.js:2:3509)
at S.fn.init.map (jquery-3.5.1.min.js:2:1508)
at La (datatables.min.js:45:79)
at f (datatables.min.js:123:15)
at HTMLTableElement.<anonymous> (datatables.min.js:123:198)
at Function.each (jquery-3.5.1.min.js:2:2976)
fb # datatables.min.js:50
ia # datatables.min.js:45
(anonymous) # datatables.min.js:45
(anonymous) # jquery-3.5.1.min.js:2
map # jquery-3.5.1.min.js:2
map # jquery-3.5.1.min.js:2
La # datatables.min.js:45
f # datatables.min.js:123
(anonymous) # datatables.min.js:123
each # jquery-3.5.1.min.js:2
each # jquery-3.5.1.min.js:2
u # datatables.min.js:113
(anonymous) # (index):2999
setTimeout (async)
(anonymous) # (index):2997
e # jquery-3.5.1.min.js:2
t # jquery-3.5.1.min.js:2
setTimeout (async)
(anonymous) # jquery-3.5.1.min.js:2
c # jquery-3.5.1.min.js:2
fireWith # jquery-3.5.1.min.js:2
fire # jquery-3.5.1.min.js:2
c # jquery-3.5.1.min.js:2
fireWith # jquery-3.5.1.min.js:2
ready # jquery-3.5.1.min.js:2
B # jquery-3.5.1.min.js:2
Datatables is notoriously buggy, and this error is well-known and can be caused by 'a number of different table configurations that the Datatables devs simply don't want to support. Fortunately, the fix is simple. I need to find where my Datatables call is and modify it to ignore that table.
Unfortunately, the earliest line in the traceback goes to a jQuery call. Nowhere does it touch any of my custom application Javascript, so I can't locate that call in my application code, so I have no idea where it's happening. The call itself isn't even easily recognizable anywhere in my code.
Presumably, I'm launching a jQuery event somewhere, which is touching or updating a table, which is then triggering a Datatables update, causing the error, and because of the use of asynchronous events, the original line of the code is being hidden.
How do I find this?
Hey Everyone I keep getting this error when trying to retrieve data from the server side using Axios. I have flushed my dns etc... cleared browser data but nothings working any idea? thank you
GET http://locahost:5000/api/activities net::ERR_NAME_NOT_RESOLVED
dispatchXhrRequest # xhr.js:184
xhrAdapter # xhr.js:13
dispatchRequest # dispatchRequest.js:52
Promise.then (async)
request # Axios.js:61
Axios.<computed> # Axios.js:76
wrap # bind.js:9
getAllActivities # agent.js:19
(anonymous) # App.js:22
commitHookEffectListMount # react-dom.development.js:19731
commitPassiveHookEffects # react-dom.development.js:19769
callCallback # react-dom.development.js:188
invokeGuardedCallbackDev # react-dom.development.js:237
invokeGuardedCallback # react-dom.development.js:292
flushPassiveEffectsImpl # react-dom.development.js:22853
unstable_runWithPriority # scheduler.development.js:653
runWithPriority$1 # react-dom.development.js:11039
flushPassiveEffects # react-dom.development.js:22820
(anonymous) # react-dom.development.js:22699
workLoop # scheduler.development.js:597
flushWork # scheduler.development.js:552
performWorkUntilDeadline # scheduler.development.js:164````
For those who missed - there's typo in locahost. Should be localhost, or locahost should be configured to resolve locally to 127.0.0.1 (or whatever target IP is, depends on OS used)
I am trying to get a Strapi.io installation set up so that it works on an existing Apache site running on Port 80.
Details:
The Strapi server is running on Port 1337.
The Strapi server has both a front page at / and an admin panel /admin
My Apache site is running at http://example.com on port 80
I have edited my apache configuration file and added the following lines:
ProxyPass /admin http://localhost:1337/admin
ProxyPassReverse /admin http://localhost:1337/admin
ProxyPass /api http://localhost:1337/
ProxyPassReverse /api http://localhost:1337/
Currently that works fine for the /api page, but not the admin page. On the Admin page I get the following console errors:
main.js:40 Uncaught (in promise) SyntaxError: Unexpected token < in
JSON at position 0
at r (main.js:40) r # main.js:40 Promise.then (async) u # main.js:1 ./node_modules/strapi-helper-plugin/lib/src/app.js #
main.js:40 t # main.js:1 (anonymous) # main.js:1 (anonymous) #
main.js:1
main.js:45 Uncaught (in promise) SyntaxError: Unexpected
token < in JSON at position 0
at t (main.js:45) t # main.js:45 Promise.then (async) u # main.js:1 ./node_modules/strapi-helper-plugin/lib/src/app.js #
main.js:45 a # main.js:1 (anonymous) # main.js:1 (anonymous) #
main.js:1 main.js:40 Uncaught (in promise) SyntaxError: Unexpected
token < in JSON at position 0
at n (main.js:40)
If I refresh the page, some or all of the main.js show as admin.js. Not sure if it makes a difference:
main.js:40 Uncaught (in promise) SyntaxError: Unexpected token < in
JSON at position 0
at r (main.js:40) r # main.js:40 Promise.then (async) u # main.js:1 ./node_modules/strapi-helper-plugin/lib/src/app.js #
main.js:40 t # main.js:1 (anonymous) # main.js:1 (anonymous) #
main.js:1
admin:1 Uncaught (in promise) SyntaxError: Unexpected token
< in JSON at position 0 Promise.then (async) u # main.js:1
./node_modules/strapi-helper-plugin/lib/src/app.js # main.js:40 t #
main.js:1 (anonymous) # main.js:1 (anonymous) # main.js:1
admin:1
Uncaught (in promise) SyntaxError: Unexpected token < in JSON at
position 0
Why am I experiencing this problem. What do I have to do to get this working correctly with my Apache server?
To clarify:
This was a very simple two minute install. I have not started to add any content to the site yet. I'm just trying to get the admin panel to work through Apache.
Apache serves by default index.html in response to any request it gets.
Therefore, my first thoughts would be adding
DirectoryIndex disabled
to .htaccess, since strapi.io API runs at / root folder and apache returns the default Apache .html file instead, which is overriding the API request.
What is happening there exactly?
1.- Your JavaScript App (strapi.io) asks for data.json at your API point and it gets the contents of an index.html.
2.- Since the contents of index.html are not JSON, and start with a <, it throws the error message. A JSON file cannot start with <.
You're probably running into issues because Strapi doesn't currently implement URL prefixes.
To get around this, you will probably want to use a subdomain or run Strapi on port 80 from the root directory with "/" instead of "/api". If you have other projects or apps on the same Apache server, you can use ProxyPassMatch to ignore those paths. For example:
ProxyPassMatch ^/otherproject !
ProxyPass "/" http://localhost:1337/
ProxyPassReverse "/" http://localhost:1337/
In this case the "/admin" route will also work without further modifications.
Alternatively, some people use Strapi middleware to apply prefixes to their routes (see example here).
reset.css Failed to load resource: the server responded with a status of 404 (Not Found)
jquery-migrate.js:23 JQMIGRATE: Migrate is installed with logging active, version 1.4.1
jquery-migrate.js:45 JQMIGRATE: jQuery.fn.load() is deprecated
migrateWarn # jquery-migrate.js:45
jquery-migrate.js:47 console.trace
migrateWarn # jquery-migrate.js:47
reset.css Failed to load resource: the server responded with a status of 404 (Not Found)
More info:
Some of my plugins' Javascript is not working but only on the home page. I've tried disabling all non-related plugins but this doesn't solve the problem.
jquery-migrate.js appears to be located in wp-includes/js/jquery/. I'm assuming this is the correct file location.
In the very beginning I including a file called reset.css but long ago deleted the file plus any reference to it (for example, in functions.php) so I'm not sure what the issue is there. It is correct that the file is not available but it also shouldn't be looking for it.
Can any tell me step by step what I need to do/change? If any other info necessary please ask! Many thanks.
EDIT: after deactivating debugging in wp-config the console changed to this:
GET http://match.onesquad.nl/wp-content/themes/match-theme/reset.css
jquery-migrate.js?ver=1.4.1:23 JQMIGRATE: Migrate is installed with logging active, version 1.4.1
jquery-migrate.js?ver=1.4.1:45 JQMIGRATE: jQuery.fn.load() is deprecated
migrateWarn # jquery-migrate.js?ver=1.4.1:45
jQuery.fn.(anonymous function) # jquery-migrate.js?ver=1.4.1:560
(anonymous) # (index):368
i # jquery.js?ver=1.12.4:2
fireWith # jquery.js?ver=1.12.4:2
ready # jquery.js?ver=1.12.4:2
K # jquery.js?ver=1.12.4:2
jquery-migrate.js?ver=1.4.1:47 console.trace
migrateWarn # jquery-migrate.js?ver=1.4.1:47
jQuery.fn.(anonymous function) # jquery-migrate.js?ver=1.4.1:560
(anonymous) # (index):368
i # jquery.js?ver=1.12.4:2
fireWith # jquery.js?ver=1.12.4:2
ready # jquery.js?ver=1.12.4:2
K # jquery.js?ver=1.12.4:2
Followed the FaceBook /Parse guide for letting users login via Fb, getting this message currently? I've looked for other examples, but can't see anything else that looks relevant.
Has anyone come across and solved this before?
POST https://api.parse.com/1/users 400 (Bad Request)b._ajax.j # parse-1.4.2.min.js:1b._ajax # parse-1.4.2.min.js:1(anonymous function) # parse-1.4.2.min.js:1c.extend.then.e # parse-1.4.2.min.js:3(anonymous function) # parse-1.4.2.min.js:3c.extend.then.g # parse-1.4.2.min.js:3c.extend.then # parse-1.4.2.min.js:3b._request # parse-1.4.2.min.js:1(anonymous function) # parse-1.4.2.min.js:3(anonymous function) # parse-1.4.2.min.js:3c.extend.then.e # parse-1.4.2.min.js:3(anonymous function) # parse-1.4.2.min.js:3c.extend.then.g # parse-1.4.2.min.js:3c.extend.then # parse-1.4.2.min.js:3c.extend._continueWith # parse-1.4.2.min.js:3c.extend.save # parse-1.4.2.min.js:3b.User.b.Object.extend.save # parse-1.4.2.min.js:5b.User.b.Object.extend._linkWith # parse-1.4.2.min.js:5b.User.b.Object.extend._linkWith.a.authenticate.success # parse-1.4.2.min.js:5g.authenticate.FB.login.scope # parse-1.4.2.min.js:5window.FB.u.__wrapper # all.js:95(anonymous function) # all.js:91window.FB.ha._xdRecv # all.js:113(anonymous function) # all.js:113pa # all.js:90(anonymous function) # all.js:88window.FB.h.setWrapper.j # all.js:50window.FB.h.setWrapper.j # all.js:50
This was caused my the fact that I'd deleted the Fb app and created a new one and not switched over the secret question and app id in the parse.com back end. Bit stupid to forget this, but someone else might find this handy one day..