Access PostgreSQL apache

69 views
Skip to first unread message

Phillip jan

unread,
Mar 25, 2022, 8:52:00 AM3/25/22
to DSpace Technical Support
Hi!

I created a dspace admin (which is saved on eperson). I can login with it on [domain name]:8080/server, but I cannot login using apache's servername ([domain name]/server). What seems to be causing this? I think the requests is sent to tomcat but tomcat cant seem to reach postgresql. Can someone help me? thanks.

Tim Donohue

unread,
Mar 25, 2022, 10:34:06 AM3/25/22
to DSpace Technical Support
You'd need to look for the underlying error message, which will either be in the User Interface or the backend logs.  Here's our troubleshooting guide: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Without the underlying error message, it's almost impossible for anyone to help.  The underlying error message will tell others what is going on in your system.

Once you find it, you can check if it's already something someone has encountered by searching this list.  If not, then send it to this list for more support.

Tim

Phillip jan

unread,
Mar 30, 2022, 12:26:08 AM3/30/22
to DSpace Technical Support
Hi!

I have successfully setup a reverse proxy on both apache/tomcat and both port 80 and 443 loads the REST API. I have already got my SSL certificate from certbot and I've configured a virtualhost that listens on 443However, admin login works only if i use a virtualhost that is running on port 80 but not when I login on a virtualhost that is running on port 443 (with ssl). Basically, I can only login to my REST API only if it is on HTTP but not when it is on HTTPS.

I checked my access logs and it returns: 

127.0.0.1 - - [time/date] "POST /server/api/authn/login HTTP/1.1" 403 501 "https://[domainname]server/login.html" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 Safari/537.36"


Additional Info:

my /etc/hosts looks like,

127.0.0.1    [domain name]
127.0.0.1    localhost
private IPV4    [domain name]

Mark H. Wood

unread,
Mar 30, 2022, 7:27:55 AM3/30/22
to dspac...@googlegroups.com
On Tue, Mar 29, 2022 at 09:26:07PM -0700, Phillip jan wrote:
> I have successfully setup a reverse proxy on both apache/tomcat and both
> port 80 and 443 loads the REST API. I have already got my SSL certificate
> from certbot and I've configured a virtualhost that listens on 443However,
> admin login works only if i use a virtualhost that is running on port 80
> but not when I login on a virtualhost that is running on port 443 (with
> ssl). Basically, I can only login to my REST API only if it is on HTTP but
> not when it is on HTTPS.
>
> I checked my access logs and it returns:
>
> 127.0.0.1 - - [time/date] "POST /server/api/authn/login HTTP/1.1" 403 501
> "https://[domainname]server/login.html" "Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 Safari/537.36"
>
>
> Additional Info:
>
> my /etc/hosts looks like,
>
> 127.0.0.1 [domain name]
> 127.0.0.1 localhost
> private IPV4 [domain name]

HTTP 403 means that the server is configured to refuse access to that
path by that host on that port. Your HTTP and HTTPS configurations do
not have the same access rules set.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
signature.asc
Reply all
Reply to author
Forward
0 new messages