Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Aplications / Re: New node application to main domain instead of subdomain throws a 503 error
« on: November 30, 2023, 11:13:10 PM »
Thank you so much for your reply.
You are right, the server configuration was overwritten. The port was set to 444! I reset it to 443 and rebuilt as you described!
Fixed
You are right, the server configuration was overwritten. The port was set to 444! I reset it to 443 and rebuilt as you described!
Fixed
2
Aplications / Re: New node application to main domain instead of subdomain throws a 503 error
« on: November 30, 2023, 04:55:34 PM »
After checking apache logs I've found the following error
[Thu Nov 30 17:50:20.194568 2023] [proxy_http:error] [pid 2440:tid 140156082267904] [client 62.xxx.xxx.xxx:41462] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Thu Nov 30 17:50:20.194568 2023] [proxy_http:error] [pid 2440:tid 140156082267904] [client 62.xxx.xxx.xxx:41462] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
3
Aplications / Re: New node application to main domain instead of subdomain throws a 503 error
« on: November 30, 2023, 12:45:01 PM »
yes, this domain is under an user. I have a few important things here.
this script is a small telegram bot (linked with father bot), no network adjustment where needed. it looks like when I changed the node application URL, some DNS config changed. am I right? I can´t figure out what exactly
I've attached an image with the only config I changed for this to happen
this script is a small telegram bot (linked with father bot), no network adjustment where needed. it looks like when I changed the node application URL, some DNS config changed. am I right? I can´t figure out what exactly
I've attached an image with the only config I changed for this to happen
4
Aplications / New node application to main domain instead of subdomain throws a 503 error
« on: November 29, 2023, 11:14:29 PM »
Hi,
I deployed a new small script running on node on my VPS running. The problem was that I used the main domain URL instead of a subdomain created for this goal. Now when I browse to the main domain I get a 503 Service unavailable.
I've created the new domain for this application but I don´t know how to set the domain back as it was before
I'd appreciate any advice.
I deployed a new small script running on node on my VPS running. The problem was that I used the main domain URL instead of a subdomain created for this goal. Now when I browse to the main domain I get a 503 Service unavailable.
I've created the new domain for this application but I don´t know how to set the domain back as it was before
I'd appreciate any advice.
5
CentOS 7 Problems / Re: Can't start Mysql Server
« on: July 31, 2023, 12:21:50 PM »
I had to reboot my server (VPS)
6
CentOS 7 Problems / Re: Can't start Mysql Server
« on: July 31, 2023, 12:13:38 PM »
I had exactly the same error after updating the php version to 7.4
Afterwards I restart apache and a couple more of services and I got into this error.
I have already checked the db user and password and it matches in both files.
Afterwards I restart apache and a couple more of services and I got into this error.
I have already checked the db user and password and it matches in both files.
7
CentOS 7 Problems / Re: Node installation
« on: March 24, 2023, 04:09:51 PM »
A collegue just helped me.
I just needed to execute node and npm from the path. In the nodejs manager version selection page, in the web control panel, there's a button to show the path where node was intalled.
So instead of just executing "npm whatever" I had to execute "/opt/nvm/versions/node/v14.21.3/bin/npm whatever"
I just needed to execute node and npm from the path. In the nodejs manager version selection page, in the web control panel, there's a button to show the path where node was intalled.
So instead of just executing "npm whatever" I had to execute "/opt/nvm/versions/node/v14.21.3/bin/npm whatever"
8
CentOS 7 Problems / Node installation
« on: March 24, 2023, 03:10:14 AM »
Hi,
I'm trying to deploy my react website. I need to run npm once ssh connected, but I get the following error:
I got that same error with command "node --version"
I already have installed node via web panel node.js manager, actually I have a nodejs api running in a subdomain with node 14.x version.
¿What am I missing to have node and npm available?
I'm trying to deploy my react website. I need to run npm once ssh connected, but I get the following error:
Code: [Select]
node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)
node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by node)
node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node)
node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by node)I got that same error with command "node --version"
I already have installed node via web panel node.js manager, actually I have a nodejs api running in a subdomain with node 14.x version.
¿What am I missing to have node and npm available?
Pages: [1]
