Changing Localhost to Public IP in DSpace Configuration

116 views
Skip to first unread message

Central Library

unread,
Oct 3, 2024, 6:06:51 AM10/3/24
to DSpace Technical Support

Dear DSpace Community,

I am trying to change the localhost configuration to a public IP in DSpace, but the changes are not reflecting. Here are the modifications I have made:

Files changed:

  1. dspace.cfg (located at build/DSpace/dspace/config/dspace.cfg)
  2. config.yml:
    • ui:
      • ssl: false
      • host:  172.21.18.16
      • port: 4000
      • nameSpace: /

Despite these changes, the public IP is not being reflected. Could you please provide guidance on how to resolve this issue? 


Thanks and Regards

A.Muthuraj

Assistant Librarian

Amrita University


DSpace Technical Support

unread,
Oct 3, 2024, 12:01:55 PM10/3/24
to DSpace Technical Support
Hi,

You should follow the documentation for how to setup a production installation.  This *requires* HTTPS support, and it will be much easier if you define a domain name (instead of just using IP addresses).  I suspect the IP address approach will not work because you cannot easily use HTTPS with an IP address.

For the backend, see step 17 which talks about how to set this up using either Apache HTTPD or NGinx: https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation

For the frontend, see step 8 which talks about how to set this up using that same Apache HTTPD or NGinx: https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation

You also should look at our troubleshooting guide to locate any errors that may be occurring (including communication errors between the frontend & backend).  We have additional hints/tips for many common errors in our Common Installation Issues guide: https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues

Tim

Central Library

unread,
Oct 17, 2024, 10:18:36 AM10/17/24
to DSpace Technical Support
Dear Dspace Community

As per your suggestions, I tried to install Apache HTTPD and attempted to start Apache2, but it did not start. The following error was shown when I ran sudo systemctl start apache2:

"Job for apache2.service failed because the control process exited with error code. See 'systemctl status apache2.service' and 'journalctl -xeu apache2.service' for details."

Could you please provide guidance on how to resolve this issue?


--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/7cbbd4cf-dace-4003-81a1-72043325469dn%40googlegroups.com.

mw...@iu.edu

unread,
Oct 17, 2024, 11:18:30 AM10/17/24
to dspac...@googlegroups.com
On Thu, Oct 17, 2024 at 02:18:18PM +0000, Central Library wrote:
> You don't often get email from centrall...@gmail.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
> Dear Dspace Community
>
>
> As per your suggestions, I tried to install Apache HTTPD and attempted to start Apache2, but it did not start. The following error was shown when I ran sudo systemctl start apache2:
>
> "Job for apache2.service failed because the control process exited with error code. See 'systemctl status apache2.service' and 'journalctl -xeu apache2.service' for details."
>
> Could you please provide guidance on how to resolve this issue?

The first step of that guidance was already provided by systemctl:
when something fails to start, inspect the logs for clues. (On a
system managed with systemd that is what journalctl is for.)

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
library.indianapolis.iu.edu
signature.asc

Roberto Greiner

unread,
Oct 17, 2024, 11:19:41 AM10/17/24
to DSpace Technical Support
After a few days trying, I managed to make exactly that work following this tutorial (it goes straight into https):

That page then points to the tutorial itself. The link is on the page, or you can go directly on:

So, my suggestion is: Go back back to the basic and make sure http://localhost:4000 is working. After that, go to this other tutorial and make https work.

Central Library

unread,
Oct 18, 2024, 5:00:09 AM10/18/24
to Roberto Greiner, DSpace Technical Support
Dear DSpace Community

Thank you for sharing the document. I received the same document link in another query. I accessed the mentioned link yesterday, but it is not opening now. If you have any documentation, please share it.

As per the document, I tried to install Apache HTTPD, and it is now working. I have attached a screenshot showing that the domain dspace.av.amrita.edu is functioning. After updating the DNS, I tried to create a certificate, but it showed an error. Below, I have mentioned the command and the results.

sudo certbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): dspace.av.amrita.edu
Requesting a certificate for dspace.av.amrita.edu

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
  Domain: dspace.av.amrita.edu
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up A for dspace.av.amrita.edu - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for dspace.av.amrita.edu - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.


To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/cc5970d1-5a61-425d-a40c-70e2cdaa36ffn%40googlegroups.com.

Michael Plate

unread,
Oct 18, 2024, 5:49:50 AM10/18/24
to dspac...@googlegroups.com
Hi,

Am 18.10.24 um 10:59 schrieb Central Library:
[…]
> As per the document, I tried to install Apache HTTPD, and it is now
> working. I have attached a screenshot showing that the domain /
> dspace.av.amrita.edu <http://dspace.av.amrita.edu>/ is functioning.
> After updating the DNS, I tried to create a certificate, but it showed
> an error. Below, I have mentioned the command and the results.
[…]

this domain is not functioning, at least not from over here.
For getting a certificate from certbot, it must be resolvable worldwide.

Try it on command line

nslookup dspace.av.amrita.edu 8.8.8.8

(8.8.8.8 is Googles' public DNS resolver, not your own, important)

or in a webtool (e.g. mxtoolbox.com)

You must register the name with your computer center, which runs a DNS
Server for that (e.g. ns3.amrita.edu)

However, worldwide availability can take a day (which should not be the
case today any more)…

Michael

Roberto Greiner

unread,
Oct 18, 2024, 7:26:58 AM10/18/24
to DSpace Technical Support

The message here says what the problem is:

-- 
  -----------------------------------------------------
                Marcos Roberto Greiner

   Os otimistas acham que estamos no melhor dos mundos
    Os pessimistas tem medo de que isto seja verdade
                             James Branch Cabell
  -----------------------------------------------------
Reply all
Reply to author
Forward
0 new messages