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).
Related
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.
I am getting a very strange error in my react build that just breaks everything and all I see is a blank page.
This is the error:
Uncaught TypeError: function call() { [native code] } is not a function!
at 128.4c993361.chunk.js:1
at B (128.4c993361.chunk.js:1)
at e (128.4c993361.chunk.js:1)
at 128.4c993361.chunk.js:1
at Object.<anonymous> (128.4c993361.chunk.js:1)
at Object.<anonymous> (128.4c993361.chunk.js:1)
at l ((index):1)
at Module.701 (main.af07ead1.chunk.js:1)
at l ((index):1)
at Module.827 (main.af07ead1.chunk.js:1)
(anonymous) # 128.4c993361.chunk.js:1
B # 128.4c993361.chunk.js:1
e # 128.4c993361.chunk.js:1
(anonymous) # 128.4c993361.chunk.js:1
(anonymous) # 128.4c993361.chunk.js:1
(anonymous) # 128.4c993361.chunk.js:1
l # (index):1
701 # main.af07ead1.chunk.js:1
l # (index):1
827 # main.af07ead1.chunk.js:1
l # (index):1
826 # main.af07ead1.chunk.js:1
l # (index):1
b # (index):1
e # (index):1
(anonymous) # main.af07ead1.chunk.js:1
Usually, if it's an error in my code react just displays a message with a link with the error details but in this case, it seems that it's an error from the build.
I tried to re-build the project and after that I removed the node_modules folder and ran npm install again but I keep getting that error.
I can't see this error when I run the project locally and it works perfectly fine when I use npm start.
I've build the project on my machine, locally and I'm getting the same error with my local build.
Is there any way to debug it so I can see what exactly is causing this error?
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
After section 8 (user accounts) in Meteor Angular 2 tutorial (social app) nothing is shown on the browser and in F12 I get this error:
install.js:85 Uncaught Error: Cannot find module 'meteor/accounts-base'require # install.js:85meteorInstall.node_modules.angular2-meteor-accounts-ui.build.login-buttons.js # login-buttons.js:13fileEvaluate # install.js:153require # install.js:82meteorInstall.node_modules.angular2-meteor-accounts-ui.build.index.js # index.js:5fileEvaluate # install.js:153require # install.js:82meteorInstall.client.imports.parties-list.parties-list.js # parties-list.ts:6fileEvaluate # install.js:153require # install.js:82meteorInstall.client.imports.parties-list.parties-list.ts # parties-list.ts:1fileEvaluate # install.js:153require # install.js:82meteorInstall.client.app.js # app.ts:6fileEvaluate # install.js:153require # install.js:82(anonymous function) # parties.ts:22
The referenced meteor/accounts-base module is a direct dependency of the accounts-password package. Step 8 of the Socially - A Meteor-Angular Tutorial App tutorial requires the installation of the accounts-password package, which will in turn install the accounts-base package. Make sure you've run the following:
meteor add accounts-password
To make sure it's installed, look in your .meteor/versions file for a matching accounts-base#X.X.X line.
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..