Seems like it is either a browser or a connection issue. Try another
browser or go into Incognito/InPrivate/Private mode and try it.
On Tuesday, November 22, 2022 at 10:13:28 PM UTC+3 Night Librarian wrote:
> I have 7.4 on Ubuntu 20.04, with Tomcat 9. I can view pdfs in the browser
> but
Hi Sonia,
It is what Michael says it is but you need to create a SAN certificate to
satisfy Chromium based browsers. To do that just follow the steps you see
below.
# I'm assuming you have installed Apache in C:\Apache24 if that's not where
you installed it you need to change the path to
On Tuesday, November 1, 2022 at 9:53:55 PM UTC+3 Tim Donohue wrote:
> Hi Sonia,
>
> Because of how cookies work in modern web browsers (Safari, Firefox,
> Chrome, all of them), unfortunately it's *not possible* to run the DSpace
> v7 REST API under HTTP *unless your only client is the same
On Friday, November 18, 2022 at 10:57:03 PM UTC+3 edmund@gmail.com
wrote:
> You will need to implement https unless you are running in a local network
>
You can try this setup and will see it is working despite Tim's posts on
it. Try it
http.
Maybe this post would help you achieving what you have in mind. Check the
first part of it
out https://groups.google.com/g/dspace-tech/c/UwMvhb6QWnk/m/02Ot51vwAQAJ
On Thursday, November 17, 2022 at 1:43:00 PM UTC+3 mcasals...@gmail.com
wrote:
> Hi,
> I'm currently trying to make a demo with a
ronment suggestion, but still got the
>>> 'unable to verify the first certificate' error.)
>>>
>>
>> The attached bundle file should do it or if you prefer you can use
>> /etc/certs/crdb.dut.ac.za/chain.pem instead if the certificate installed
>> on the F5 ap
If your apache SSL configuration is correct you can force the NodeJS and
the starting of the service later to access crdb.dut.ac.za directly using
the server local IP instead of going thru the Public-IP/F5. You can do it
by adding an entry into /etc/hosts for the server private IP address. The
Your configuration you posted here
https://github.com/DSpace/DSpace/issues/8200 is a total mess. Maybe you
should clean it too.
On Monday, March 14, 2022 at 5:47:30 PM UTC+3 wolfgang t. wrote:
> THANK YOU, that was it!!!
>
> Tim Donohue schrieb am Montag, 14. März 2022 um 15:18:18 UTC+1:
>
>>
Try this also see a version of it in a text format attached in case of
copying of this thread will develop hidden characters :
1) Settings in dspace.cfg or local.cfg:
dspace.server.url = https://dspace.umiz.at/server
dspace.ui.url = https://dspace.umiz.at
solr.server = http://localhost:8983/solr
iled with exit code 1.
> info Visit https://yarnpkg.com/en/docs/cli/run for documentation about
> this command.
>
> El domingo, 13 de marzo de 2022 a las 12:59:00 UTC-5, Mohammad S.
> AlMutairi escribió:
>
>> I think you forgot to stop the frontend service bef
I think you forgot to stop the frontend service before you start the
compiling again. To resolve it do one of the commands you see below and
then just the frontend with ( yarn serve:ssr ).
a) pm2 kill
b) kill -9 $(lsof -t -i :4000)
--
All messages to this mailing list should adhere to the Code
It's Impractical but you still can make the domain verification somewhere
else on any publicly accessible server that you control if you point your
domain to that server IP address and ran the same previous command. You
then need to copy the generated 90 days valid certificates to your Windows
It's debatable but a bad idea in general unless you doing it for testing
purposes and temporarily. It's much safer to get a ( Linux - NO Windows )
server in one of the public clouds and run dspace on it for whatever
purpose you intend to run it for.
Good luck
On Friday, March 11, 2022 at
Out of the box added custom metadata to submitted/uploaded/ingested items
should be searchable if Solr discovery is reindexed after the items are
submitted ( [dspace]/bin/dspace index-discovery ). I had no problem finding
any custom added metadata or the specific values of these metadata's
or let's encrypt style too.
>
> thanks again
>
> Nicolas
>
>
>
>
>
> El mié, 9 mar 2022 a la(s) 17:22, Mohammad S. AlMutairi (alo...@gmail.com)
> escribió:
>
>> On Wednesday, March 9, 2022 at 9:58:15 PM UTC+3 ing.nicola...@gmail.com
>> wrote:
It can found in the language file you are using ( en.json5 ) in following
folder [dspace-angular]/src/assets/i18n/
On Tuesday, March 8, 2022 at 8:25:01 PM UTC+3 tese...@gmail.com wrote:
> Dear Teams, how can I change "*DSpace Angular" *title on the browser
> page next to favicon as shown in
It's possible but you have to provide more details. In general you can use
one of DSpace predefined Metadata Schema (
https://you-dspace-server-url/admin/registries/metadata ) or you can add
your own. Read about it in the documentation
here
On Wednesday, March 9, 2022 at 9:58:15 PM UTC+3 ing.nicola...@gmail.com
wrote:
> really, i'm getting crazy
>
You shouldn't be. There is always a technical explanation to what you think
is weird to happen. I guess it has to do to the way you setup your dspace
environment but you haven't
On Wednesday, March 9, 2022 at 1:47:31 PM UTC+3 phillip...@gmail.com wrote:
> Yes, it asked for a path. I don't know what I should input into it. What
> path should I include here? thanks!!
httpd.conf path is what you suppose to write as a path there ( It needs to
fetch the ServerName value
It's a very bad idea to run Dspace or any other service unsecure (
Traffic including login credentials can be sniffed very easily ) but if you
insist on doing it It's possible to run it via HTTP ( See the setup that
should work for you below ). The issue with the latest browsers builds (
Hello,
I'm guessing here.
Double check and see if solr cores installation is O.K
curl http://localhost:8983/solr/admin/cores
Try re-building the index.
/opt/dspace/bin/dspace index-discovery -h
On Thursday, February 10, 2022 at 12:40:02 AM UTC+3 sto...@hope.ac.uk wrote:
> Hello All,
>
> I
Hello,
run this command from the console curl
http://localhost:8983/solr/admin/cores ... What do you see?
On Thursday, February 10, 2022 at 12:40:02 AM UTC+3 sto...@hope.ac.uk wrote:
> Hello All,
>
> I upgraded our 6.3 site to 7.1.1, after some configuration issues I did
> manage to get it up
On Wednesday, February 9, 2022 at 2:47:08 AM UTC+3 Chris Clawson wrote:
> Everything seemed to finish well, although a full system reboot failed to
> start angular as a service. I guess this is my last barrier to a
> functional upgrade, but it is the stuff of a new thread if I need help.
>
On Tuesday, February 8, 2022 at 7:23:55 PM UTC+3 Mark H. Wood wrote:
> Well, Ubuntu Focal has Solr in its package repository, but it's a
> decade old, so Ubuntu is one of the distro.s on which you need to do
> the installation manually. That means you'll need to create a user to
> run it, very
On Monday, February 7, 2022 at 4:14:26 PM UTC+3 Mark H. Wood wrote:
> The three processes (dspace-server-webapp, dspace-angular, solr)
> interact only through network connections. They do not need direct
> access to each others' files, and I would argue that they *should
> not* have direct
ribution to the community trying to
save anyone's time.
Regards.
On Monday, February 7, 2022 at 10:09:45 AM UTC+3 Jaware wrote:
> Dear AlMutairi,
> Fantastic explanation.It works based on your comment
>
> Thanks again,
>
> Best,Jaware
>
>
> On Sat, Feb 5, 2022 at 2:22 PM Mohammad
Hello everyone,
I need to confirm this to the community. Whenever this error
'error.top-level-communities' do show up on the front page ( should be
added to the common installation issues wiki ) Solr is either not installed
or misconfigured. To resolve it on the Ubuntu Linux servers just
r pointing that out. The names of the attributes
>> are unmatched. After changing the attribute names, it is working now. Thank
>> you so much.
>>
>>
>> Joshua Kim
>> Web Developer, Library IT
>> Library, Museums and Press
>> University
Hi,
You welcome. I really can't explain it without knowing the operating system
you are using, seeing the webserver configuration file and looking ate the
self signed certificate information you were using ( Post them here if your
would to have a look on them ). My initial guess it was failing
Hello Andrei,
I think you got it confused here by setting up the self signed certificate
and using the IP address to access your server ( What did you choose for
the common name of your self signed certificate? - The IP address? it can
be but usually the servers names not the IP addresses ).
Glad it worked for you Chris.
Cheers
On Tuesday, February 1, 2022 at 3:01:29 AM UTC+3 Chris Clawson wrote:
> Solid advice and now I have working features! I was unable to find
> critical details for my setup until Mohammad took the time to explain the
> detail and provide specific, working
Hello,
It shouldn't be if the purge and the curl commands were executed
successfully. Did you see any error when you executed them?
I see now how you installing the nodejs package. Version v10.19.0 is the
default nodejs version if you used Ubuntu 20.04 default repository files.
It's better to
Sorry to see you still facing an issue with the image server. Just follow
the steps to get it working. I had to separate the virtual hosting config
files because (a) Frontend reverse-proxy settings conflicts with the image
server setting (b) To save you some bucks buying a newer certificate.
Glad I was of a help to you.
Cheers
On Friday, January 28, 2022 at 3:35:52 PM UTC+3
raf...@faculdadesensu.edu.br wrote:
>
> Good morning, thanks for the reply Tim Donohue and alo...@gmail.com, your
> explanation made me see the problem more clearly thank you. The problem
> really was in
He needs to remove the old nodejs package and also remove the Node.js 10.x
distributions repository file before upgrading to the new version. He can
do this:
1) sudo apt purge nodejs
2) sudo rm -rf /etc/apt/sources.list.d/nodesource.list
3) sudo curl -sL https://deb.nodesource.com/setup_14.x |
This error ( at the end of page there is error.top-level-communities ) is
a good indication Solr is not installed/setup correctly on your server.
On Wednesday, January 26, 2022 at 6:24:34 PM UTC+3 Tim Donohue wrote:
> The error messages that appear in the UI are "generic" and do not detail
>
It has nothing to do with the language but what should be highlighted and
where. Check this link https://solr.apache.org/guide/8_2/highlighting.html
You welcome
On Thursday, January 27, 2022 at 8:29:22 AM UTC+3 ayatr...@gmail.com wrote:
> currently I am working on dspace 7.1 and I am having
Hello,
Frontend won't be accessible because you running it on the loopback adapter
( localhost - 127.0.0.1 ). With the current frontend setup you can't access
the frontend remotely ( sort of ) but you can if you browse from the
machine where the frontend is installed. Tim directions is the way
. PDF's supposed to be downloaded just like any other
>> extensions. It all comes down to the permission you set.
>>
>> On Wednesday, January 19, 2022 at 12:19:23 AM UTC+3 Mohammad S. AlMutairi
>> wrote:
>>
>>> I still think it's a permission issue. If I were you
It's a common issue caused by how you setup DSpace. localhost usually
configured if you can access this URL locally or using a tunneled
connection for development/testing purposes.
Stackoverflow poster is using Windows server 2012. Are you using Windows?
or Linux?.
On Thursday, January 20,
Hello Chris,
For image viewing and video playing you have to enable them in
[dspace-angular]/src/environments/environment.prod.ts (scroll download to
the end of the file) and then compile the frontend to be able to view
images or stream videos on DSpace..
// Whether to enable media viewer
at 12:19:23 AM UTC+3 Mohammad S. AlMutairi
wrote:
> I still think it's a permission issue. If I were you I would have created
> a newer replica of the collection and the bitstream just to prove if it's
> caused by a misconfigured permission or not. Handle can be anything (
I still think it's a permission issue. If I were you I would have created a
newer replica of the collection and the bitstream just to prove if it's
caused by a misconfigured permission or not. Handle can be anything (
Default handle123456789 is O.K ). Try accessing it using it's UUID if in
It's a permission issue you have. By default DSpace gives Anonymous group
read access so it seems the doc's have it but not the pdf's. Double check
the permissions ( Authorization ) starting from the top
community/collections all the way to the bitstream itself. Try to search
for the bitstream
You should start from this. Read it
carefully.
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-InstallationOverview
On Wednesday, January 5, 2022 at 7:24:52 PM UTC+3 Mohammad S. AlMutairi
wrote:
> You are at the right place. The page you posted are the instructi
You are at the right place. The page you posted are the instructions you
should follow to install the frontend but before this part of installation
you should also do
this
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendRequirements
On Wednesday, January 5,
The previous link was for the backend. In DSpace 7 you also need to install
the frontend two. It's on a different page here it
is: https://github.com/DSpace/dspace-angular/releases/tag/dspace-7.1
Here is a direct link to the frontend tar.gz file:
Hello,
At the bottom of that page it says Assets. There are two links in different
formats zip and tar.gz
Here is
one https://github.com/DSpace/DSpace/archive/refs/tags/dspace-7.1.1.tar.gz
Good luck
On Wednesday, January 5, 2022 at 5:15:34 PM UTC+3 informat...@gmail.com
wrote:
> Hello
Hello,
Happy New Year,
I think this is what you looking for ( bulkedit.gui-item-limit = 20 )
. https://bit.ly/3zldj4h .. for the command line [dspace]/bin/dspace
metadata-import -h
Hope it help
On Monday, January 3, 2022 at 5:36:10 PM UTC+3 alejandr...@gmail.com wrote:
> Hello,
> I am
emoved from a previous install. I really would like
> to know my problem with my failure using 'apt-get install tomcat9'.
> Thanks for the patience. At the very least, my understanding of all this
> is becoming much more solid than it has been.
>
> On Sunday, January 2, 2022 at 11:
/tomcat/latest/conf/server.xml
On Sunday, January 2, 2022 at 7:13:22 PM UTC+3 Mohammad S. AlMutairi wrote:
> Hi Chris,
>
> Happy New Year to all.
>
> On Sat, Jan 1, 2022 at 11:01 PM Chris Clawson
> wrote:
>
>> Status and Tomcat configuration questions...
>>
>>
&g
going to need to be persuaded that upgrading his
>> project is a good idea. (So am I). I hope DSpace 7 has some great and
>> modern media handling features I can brag about. I also want to try out the
>> Jpeg2000 support. Cloud storage is expensive and some of my great Seadrago
d any language or theme file, German
>> translation json5 file is already present in the release.
>>
>> The Backend is running on the same server without any issues.
>>
>> For comparison what I did:
>>
>> apt update
>> apt install openjdk-11-jdk
&g
Hi,
I think that's not a fix to the root cause of both issues you faced ( I've
seen this temporarily tweak here https://bit.ly/3eGhZYZ ). You shouldn't
got all the issues you faced at all if all you have done was the changes
you have made into the German language file and the environment.*.ts
.
yarn run build:prod
Hope it help.
On Thu, Dec 30, 2021 at 5:26 PM Mohammad S. AlMutairi
wrote:
> On Wednesday, December 29, 2021 at 4:03:40 PM UTC+3 Chris Clawson wrote:
>
>> Mohammad:
>>
>> The DSpace installation page didn't seem to provide any specific
>> p
ice
systemctl status pm2-root.service
###
> I just got up and see that you have sent me a lot of information, related
> to the status you think my install is at this morning. Thanks and give me
> time to study it all!
>
> C.
>
T
6.3 install runs at https://montaguearchive.org:8443/ . Maybe I
> have a problem using this port. Thanks and good night.
>
> On Tuesday, December 28, 2021 at 7:03:59 PM UTC-5 Mohammad S. AlMutairi
> wrote:
>
>> It is a little bit late here. Looking at what you posted as a tomca
Is it possible to to send me the result of this command?.
grep tomcat /etc/passwd
On Wednesday, December 29, 2021 at 1:42:30 AM UTC+3 Mohammad S. AlMutairi
wrote:
> I was able to replicate the issue you have (see the attached snapshot). It
> turned out it's happening when the user
systemd[1]: Failed to start LSB: Controls Apache
> Solr as a Service.
> root@media:/build#
>
> On Tuesday, December 28, 2021 at 9:21:25 AM UTC-5 Mohammad S. AlMutairi
> wrote:
>
>> Hello Chris,
>>
>> Your solr installation is broken so you really really really
rg.apache.lucene.store.NativeFSLockFactory@12cd8c11;
maxCacheMB=48.0 maxMergeSizeMB=4.0)",
On Tuesday, December 28, 2021 at 4:56:15 PM UTC+3 Chris Clawson wrote:
> Thanks for revisiting this! There is detail here which I have never seen,
> especially step e) . I will probably attempt
A lot of newcomers who want to try DSpace specially non-technical people do
face an issue installing Solr for DSpace. The DSpace Solr installation
portion doesn't cover specific details about any Linux OS so to make things
easier for the folks who are using Ubuntu I'm posting a detailed
ave help much in
> learning where to look. Thanks!
>
> On Tuesday, December 21, 2021 at 5:43:15 PM UTC-5 Mohammad S. AlMutairi
> wrote:
>
>> Chris,
>>
>> Re-reading your message made me understand the confusion you have. Please
>> don't start solr from /o
th system
> startup.
> Might you clarify why I cannot install using this script, after I change
> the user to 'tomcat'?
>
> On Tuesday, December 21, 2021 at 5:03:48 PM UTC-5 Mohammad S. AlMutairi
> wrote:
>
>> Hello Chris,
>>
>> Enabling services so it
d also change that
> variable to 'tomcat', as I first did with the script in /build?
> Thanks - I'll 'get it' eventually
> On Monday, December 20, 2021 at 9:17:06 PM UTC-5 Mohammad S. AlMutairi
> wrote:
>
>> You most welcome. Let us here in group how it goes or if you need help
/default/' ?
> 3) Once installed, should I also edit SOLR_USER in
> '/opt/solr-8.11.1/bin/install_solr_service.sh' and also change that
> variable to 'tomcat', as I first did with the script in /build?
> Thanks - I'll 'get it' eventually
> On Monday, December 20, 2021 at 9:17:06 PM
t/' ?
> 3) Once installed, should I also edit SOLR_USER in
> '/opt/solr-8.11.1/bin/install_solr_service.sh' and also change that
> variable to 'tomcat', as I first did with the script in /build?
> Thanks - I'll 'get it' eventually
> On Monday, December 20, 2021 at 9:17:06 PM UTC-5
Hello Glenn,
Are you able to login if you disabled
authentication-password.domain.valid?. If you can not try the the following
and see if it helps if not you need to post the webserver/reverse proxy
setup and the environment.*.ts you used ( UI & REST parts). In the Chrome
Developer Tools -->
Hello,
You should've opted for a bridging configuration for dspace virtual machine
instead of Host-Only and Natting and Port Fowarding. The later config
should've worked if done right but Bridged Adapter is way better. Read
about them
here
my
>> production server (with DSpace 6.3) at https://montaguearchive.org:8443/
>> .
>> Chris
>>
>> On Monday, December 20, 2021 at 12:56:31 PM UTC-5 Mohammad S. AlMutairi
>> wrote:
>>
>>> Hello Chris,
>>>
>>> You dropped a vit
. This site is practice before attempting to upgrade my
>> production server (with DSpace 6.3) at https://montaguearchive.org:8443/
>> .
>> Chris
>>
>> On Monday, December 20, 2021 at 12:56:31 PM UTC-5 Mohammad S. AlMutairi
>> wrote:
>>
>>&g
Hello Chris,
You dropped a vital piece of information about the Linux flavor you are
using so I'm assuming a Debian derivative. It's better to start a fresh
Solr installation by removing the old Solr installation and following the
steps you see below.
a) mkdir /build
b) cd /build
c) wget
101 - 171 of 171 matches
Mail list logo
