--
> *From:* dspac...@googlegroups.com on behalf
> of Christiane Baier
> *Sent:* Tuesday, May 23, 2023 2:06 AM
> *To:* DSpace Technical Support
> *Subject:* [dspace-tech] Re: dspace-7.5. angular-ui gives no response
>
> Hi Tim,
>
> Before I posted my
se are my best ideas right now, but maybe someone else on this list would
have other brainstorms to share.
Tim
From: dspace-tech@googlegroups.com on behalf of
Christiane Baier
Sent: Tuesday, May 23, 2023 2:06 AM
To: DSpace Technical Support
Subject: [dspace-
On Tue, May 23, 2023 at 12:06:07AM -0700, Christiane Baier wrote:
> Before I posted my problem here I tried everything as as outlined in
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
>
> It is not working without pm2.
>
>
Hi Tim,
Before I posted my problem here I tried everything as as outlined in
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
It is not working without pm2.
*/dspace-ui-deploy*$ node ./dist/server/main.js
Building *production* app config
Hi Christiane,
Those warnings when running "yarn install" are normal behavior. They can
be ignored. They are not causing any issues.
As I mentioned previously, you might want to try starting up the UI
*without* PM2, just to verify it's working properly standalone & trying to
access it on the
Hi there,
I decided to start with a fresh installation of the angular frontend. I
have following version installed:
npm version: 9.6.6
yarn version: 1.22.19
node version: v16.20.0
execpt for a new config.prod.yml in the config directory, with the minimal
configuration as stated in the
Hi Tim,
I went over the troubleshooting guide, but this doesn't help as I don't get
any content in the browser, so nothing to see. In the apache logs, I can
see, that the host is reached:
"GET / HTTP/1.1" 502 6753
but it hrows an error and the following is displayed in my browser:
The proxy
Hi Cristiane,
In order to help, we'd need you to look for the underlying error message
when you attempt to access the User Interface (or backend, depending on the
problem). Here's a troubleshooting guide with details on finding the
underlying
error:
