Hi everyone,
Does anyone is having some problem with CC again? In my repository the cc
step just show "no license" option.
Thanks.
Em segunda-feira, 2 de julho de 2018 17:05:00 UTC-3, Javier Távara escreveu:
>
> Hi Rob!
> Our DSpace instances are having problems again due to an invalid SSL
Thank you everyone who reported this.
I am going to mark this as fixed.
We should move the API to https-only at some point in the future to help
keep user information private, but it shouldn't happen without warning.
Thanks again.
- Rob.
On Tuesday, April 3, 2018 at 11:34:44 AM UTC-7, George
Rob:
Thank you. Going back to http has fixed the problem for us at Cornell
University.
George Kozak
Cornell University
On Tue, Apr 3, 2018 at 2:01 PM, Rob Myers wrote:
> Heya all.
>
> I have re-enabled http for now. I will put a redirect back in place at
> some point
Thanks Rob, definitely the best choice.
I see the API is back online.
— Javier T.
On Apr 3, 2018, 1:04 PM -0500, Rob Myers , wrote:
> Heya all.
>
> I have re-enabled http for now. I will put a redirect back in place at some
> point in the future, with suitable
Hi again,
Yes we do too due to the CC API service being down. Before, changing the
configuration file alone to "https" worked while the API was still
available - just in case this is useful to people.
Agustina
On Tuesday, 3 April 2018 13:41:14 UTC+1, Marion Rupp wrote:
>
> Hi,
>
> We still
Heya all.
I have re-enabled http for now. I will put a redirect back in place at some
point in the future, with suitable warning.
For anyone who changing the url to be https didn't help, does switching
back to http improve things?
- Rob.
On Monday, April 2, 2018 at 5:13:57 PM UTC-7, Rob
George,
It depends on where you are doing the change. See
https://wiki.duraspace.org/display/DSPACE/Rebuild+DSpace and
https://wiki.duraspace.org/display/DSDOC5x/Ant+targets+and+options
I only make changes to [dspace-source], so I have to rebuild it for the new
config to be copied to [dspace]
I think there are still some issues on the CC side. The curl command from
Rob's message above responds with a 503 Service Unavailable. Same for just
https://api.creativecommons.org/rest/1.5. Our DSpace is still giving the
NullPointerException.
On Tuesday, April 3, 2018 at 3:43:37 AM UTC-5,
Hi all,
We have also performed the change to HTTPS for the cc.api.rooturl
configuration parameter and restarted DSpace (v5.6) and everything seems to
be working again.
Best,
Agustina
On Monday, 2 April 2018 22:31:29 UTC+1, George Kozak wrote:
>
> Hi,
> We have a DSpace 5.5 and a DSpace 6.2
Hi, Everyone:
I made the suggested change from http to https, but I still have failure in
connecting to Creative Commons. I restarted tomcat and cleared the cocoon
cache, as well.
George Kozak
Cornell University
On Mon, Apr 2, 2018 at 7:59 PM, Javier Távara wrote:
> Thank you
Heya Javier.
Thank you for checking this.
There is a 301 redirect in place from http to https.
The old server had Varnish publicly accessible on port 80, which I assumed
was an error so I didn't recreate that (we were meant to have switched
everything to https a couple of years ago!).
If
Thank you for the update Rob.
Any redirection is being applied from non-SSL to SSL? Was the same before
the update?
I changed my settings (dspace.cfg) to use SSL:
# The url to the web service API
cc.api.rooturl = https://api.creativecommons.org/rest/1.5
And it works now :)
- Javier.
El
Heya everyone, Rob from Creative Commons here.
I'm very sorry that our API isn't working with DSpace at the moment. I
upgraded the server that the API runs on, and the problem that you are
seeing wasn't caught by my tests.
If I call the API simply via the command line, e.g.:
curl -d
I saw the tweets. Thank you.
As we don't have any useful logs of what's happening, I thought
disabling/enabling the step could fire any sort of cache clearing.
No success.
- Javier
El lunes, 2 de abril de 2018, 17:33:16 (UTC-5), Keith Gilbertson escribió:
>
>
>
> On Monday, April 2, 2018 at
I really don't want to disable the CC License step.
Disabling/enabling fixes nothing by the way.
- Javier.
El lunes, 2 de abril de 2018, 16:43:29 (UTC-5), Keith Gilbertson escribió:
>
> George, we've had similar problems today. We'll probably disable CC
> License steps for now, and then
George, we've had similar problems today. We'll probably disable CC License
steps for now, and then restart Tomcat. On our system, this is configured
in /dspace/conf/item-submission.xml
--keith
On Monday, April 2, 2018 at 5:31:29 PM UTC-4, George Kozak wrote:
>
> Hi,
> We have a DSpace 5.5 and
16 matches
Mail list logo