Open alejandrogj opened 4 years ago
Hey @alejandrogj 192.168.0.164
is your superdesk server ip? It works without port?
Yes, 192.168.0.164
is the superdesk server ip. It works without port.
I installed superdesk using the installing script (https://raw.githubusercontent.com/superdesk/fireq/files/superdesk/install)
@takeit - any idea here?
@petrjasek @takeit I'm facing the same issue here, any idea?
@alejandrogj did you find anything to solve this?
@mabastaraz not yet :(
Try assigning a hostname to the servers and then use the hostname instead of IP. I had issues caused because of that. Also, did you have any trouble getting the Publisher tab to come up in Superdesk? If so, what guide did you use? I cannot seem to get it to show up...
UPDATE: Disregard above. Now I am at the same spot where you are at with the infinite loading.
@NicholasIanni Even assigning a hostname to the servers and then use the hostname instead of IP won't solve the problem of the loading screen.
I think it's all related to the configuration of superdesk.config.js inside /opt/superdesk/client, idk maybe I'm wrong!
@mabastaraz Yeah I realized that :/. Honestly more documentation on the config file would be nice. Out of curiosity did you use the updated script that was posted in the repo's issue area to install?
@NicholasIanni Yes, indeed. I installed both fresh Superdesk and Publisher today. but I have found something interesting,i have tried but didn't work. You can take a look and give us feedback.
Actually after quickly viewing my side of the console something is trying to access "example.com". There is also an issue reaching whatever is running on port 5100 so I'll also look into that if I have time tonight. I think I'm going to post a working virtual machine image for publisher and Superdesk once I get them working so people don't have to go through this process for demos and stuff.
So after reading the article you provided and looking into how things are communicating, it seems the issue definitely is surrounding WebSocket. I'm guessing there is a config problem with either the wsProtocol, wsDomain, wsPath, wsPort, or base variable. It seems that even though 8080 is defined as the port, communication is trying to be made over port 5100. I also some reference to api/v2 but I can't seem to find the was or api/v2 directory. I was hoping to deploy SD and Publisher by end of this week but something tells me we are going to have to do some digging here unless an actual dev can lead us in the right direction...Hope this info is of use. I will keep digging in the meantime.
guys - what do You have set as value in SUPERDESK_SERVERS
env (in publisher env's)?
@ahilles107
/var/www/publisher/.env.local
/opt/superdesk/client/superdesk.config.js
and you did composer symfony:dump-env prod
(or dev -if you use dev env)?
What's the response for superdesk auth request (dev tools -> tan network) ?
@ahilles107 composer symfony:dump-env prod
superdesk auth request : ws://localhost:5100/
You should have more in network tab - keep it open and refresh page. There must be some filed request to publisher.
@mabastaraz - it's problem with your publisher instance. http://publisher.kurdishtimes.net/ returns 500 error. Check publisher error log and fix issue ;)
and in cors allow origin env provide that publisher ip address - as you us it instead domain in your browser.
@ahilles107 500 Internal Server Error happens after I run composer symfony:dump-env prod
This not reason but symptoms. Check publisher/php logs to see what's wrong and fix it ;)
@ahilles107
rm .env.local.php
when I run composer symfony:dump-env prod
again
Removing computed env's will not help. Like i said - check logs and find out real problem.
Where are these logs that you are referencing located?
Publisher logs can be found at var/log/
directory inside publisher.
@ahilles107
I'm still facing the same issue after I run composer symfony:dump-env prod
and .env.local.php generated, the Sperdesk Publisher will go 500 error.
I have checked publisher logs
root@publisher:/var/log/postgresql# tail postgresql-10-main.log 2020-06-11 18:30:47.684 UTC [31101] root@publisher_prod FATAL: database "publisher_prod" does not exist 2020-06-11 18:30:47.728 UTC [31102] root@publisher_prod FATAL: database "publisher_prod" does not exist 2020-06-11 18:30:47.742 UTC [31103] root@publisher_prod FATAL: database "publisher_prod" does not exist
Just to make sure that i have right information inside /var/www/publisher/.env.local
SUPERDESK_SERVERS='["IP/Domian of Superdesk"]' /// IP/Domian of Superdesk
CORS_ALLOW_ORIGIN=http://IP/Domian of Superdesk Publisher /// IP/Domian of Superdesk Publisher
Also included a screenshot of .env.local.php
Thanks for your help :)
Hi!
I have linked Superdesk with Publisher but when i click "Publisher Settings" in Superdesk i get a never-ending loading screen. The console prints out this error
Possibly unhandled rejection: {"data":null,"status":-1,"config":{"method":"POST","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"http://192.168.0.165/api/v2/auth/superdesk/","data":{"session_id":"5eaa70bb30f3daa24f877668","token":"Basic MTI5YzQwNGItNzUwNS00YjEyLWI3MDYtMTUzMTIzODM3NGIzOg=="},"add_format":"json","headers":{"Authorization":"Basic undefined","Accept":"application/json, text/plain, */*","Content-Type":"application/json;charset=utf-8"}},"statusText":"","xhrStatus":"error"}
It seems there is something wrong whent trying to access to http://192.168.0.165/api/v2/auth/superdesk/
Publisher is installed and working in http://192.168.0.165:8000
My superdesk.config.js
and the .env.local file in Publisher
Thanks!