Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

A bad HTTP response code (404) was received when fetching the script.

Z
zerefgg Gamers last edited by
Hello,
I installed NodeBB today. Everything works fine but in my browser's console I see :
```
A bad HTTP response code (404) was received when fetching the script.
```
Using:
Mongodb
Nginx
Debian 9
VPS 2GB RAM
Reply Quote 0
1 Reply Last reply
Z
zerefgg Gamers last edited by

It seems like this fixed it:
https://github.com/vuejs-templates/webpack/issues/446#issuecomment-278503745

gazpachu created this issue in vuejs-templates/webpack

closed A bad HTTP response code (404) was received when fetching the script. #446
Reply Quote 0
1 Reply Last reply

2
Posts

121
Views

Log in to reply

Suggested Topics

unable to edit groups/bad data
Technical Support • • Brass Man

1

0
Votes

1
Posts

509
Views

A while back I restored my database from a backup, and I have a feeling that backup may have been corrupt. when I try to visit the admin/manage/groups page, my nodebb instance crashes and reboots. I get the error Cannot read property 'indexOf' of undefined. After doing a little debugging I found that that the query for groups:createtime (line 152 in src/database/mongo/sorted.ja), is returning some objects that DONT have "groups:createtime" as their key ... these documents don't have the expected schema, which is what's throwing that undefined error. I've found, using the mongo console, when I use find('_key': 'groups:createtime') I only get the objects I expect, but find('_key': \groups:createtime\) returns the bad objects (note that the substring "groups:createtime" appears nowhere in _key string for those objects). More upsettingly, if I remove those bad objects by their ObjectId, they STILL return in that query ... despite the remove command returning without error, despite no longer being able to look the object up by it's ID. I'm not clear on whether this is a NodeBB issue at all, or entirely on the Mongo side, but in the meantime, I can't edit anything in regards to groups (including adding/removing members to existing groups), and attempts at upgrading my forum version fail at the database migration step.
Yikes - 502 Bad Gateway Nginx DigitalOcean
Technical Support • • Michael Pfaff

12

0
Votes

12
Posts

2764
Views

Will try to go to this soon! Sorry. Had a busy weekend.
SOLVED Upgraded from 0.9.3 to 0.9.4 Received "GMT validator deprecated" warning
Technical Support • • rod

2

0
Votes

2
Posts

1057
Views

@rod That will be taken care of in the next release. Already fixed in the master branch. https://github.com/NodeBB/NodeBB/issues/4154 pichalite created this issue in NodeBB/NodeBB closed validator.js warning #4154
How to add some script on each page ?
Technical Support • • leksar

4

0
Votes

4
Posts

1686
Views

Thank you.
Assistance requested to reformat document.write from ad code javascript
Technical Support • • rod

4

0
Votes

4
Posts

1446
Views

@rod Ohh I see what it does... mhm since is in nodebb try: $.get('https://fsadwork.com/show.php?z=32&pl=99&j=1&code='+new Date().getTime(), function(data) { document.getElementById("YOURTAG").innerHTML = data.replace('document.write(','').replace(')','') }); <noscript> <iframe src="https://fsadwork.com/show.php?z=32&pl=99" width="920" height="120" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"></iframe> </noscript> But this probably will not work because they'll have cross-origin ajax control. And of course you need to change "YOURTAG" with the id of where you want the ads to appear. If it doesn't work.. I don't know then how could you change it

| |

Copyright © 2018 NodeBB | Contributors