getPluginSpecs error

Moralis General
#21

bron this is what Iā€™m trying to tell youā€¦

nginx is going to send anything nftea.app to localhost:3000 where the main app is runningā€¦

tried it the way you suggested like this

server {
             # Binds the TCP port 80.
             # Defines the domain or subdomain name. 
       # If no server_name is defined in a server block then 
             # Nginx uses the 'empty' name
       root /var/www/html/nftea;
       server_name nftea.app www.nftea.app;
             # Redirect the traffic to the corresponding 
             # HTTPS server block with status code 301

        location / {

        proxy_pass       http://localhost:3000;
        proxy_set_header Upgrade    $http_upgrade;
        proxy_set_header Connection $http_connection;
        proxy_set_header Host       $host;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/nftea.app/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/nftea.app/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot




}

server {

server_name nftea.app/server;

location / {

        proxy_pass       http://localhost:1337/server;
        proxy_set_header Upgrade    $http_upgrade;
        proxy_set_header Connection $http_connection;
        proxy_set_header Host       $host;
    }

}
#22

first step is to make the server accessible over the internet, without the application that connects to the server, then you will use that server url in your application

you donā€™t have to make them both at the same time to work on the same url

#23

you guys gave folks a ton more work to doā€¦

Iā€™ve been at this for 6 hours nowā€¦ need a breakā€¦ Iā€™m not paying for an extra server just to get this goingā€¦ Iā€™ll look at other solutions for now and re-write the entire freaking application after all this extra stuffā€¦

#24

you donā€™t need another server, the front end application and the parse server have to run on different locations on the same server, like the frontend on https://nftea.app/front_end and the server url on https://nftea.app/server and the front end will have to connect to the server url

you can also test it locally until you make it work

#25

coolā€¦
moved it to a different domain
futuro.money runs the parse serverā€¦
nftea.app is the frontā€¦

  <MoralisProvider appId="001" serverUrl="https://futuro.money" initializeOnMount={true}>
            <Layout>
              <Component {...pageProps} />
            </Layout>
        </MoralisProvider>

error Error: XMLHttpRequest failed: "Unable to connect to the Parse API"
#26

this one seems close to how it should work

the other one still tries to connect to http://localhost:1337/server/functions/getPluginSpecs

#27

changed to

server {
             # Binds the TCP port 80.
             # Defines the domain or subdomain name. 
       # If no server_name is defined in a server block then 
             # Nginx uses the 'empty' name
       server_name futuro.money www.futuro.money;
             # Redirect the traffic to the corresponding 
             # HTTPS server block with status code 301

        location / {

        proxy_pass       http://localhost:1337;
        proxy_set_header Upgrade    $http_upgrade;
        proxy_set_header Connection $http_connection;
        proxy_set_header Host       $host;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/futuro.money/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/futuro.money/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

<MoralisProvider appId="001" serverUrl="https://futuro.money/" initializeOnMount={true}>

looks like it works in browserā€¦ not in scriptā€¦

Screen Shot 2022-11-07 at 1.23.36 PM
Screen Shot 2022-11-07 at 1.23.36 PM926Ɨ352 33.9 KB

same cannot connect to pase API error

#28

It looks like you have to change the server url in front end code

#29

change to what?
Iā€™ve changed
REACT_APP_SERVER_URL=http://futuro.money/server

changed this

        <MoralisProvider appId="001" serverUrl="http://futuro.money/server" initializeOnMount={true}>

change what exactly?

#30

itā€™s calling the localhost:1337 from RESTController.js?26fd in node_modules/moralis/v-1

#31

anyway to overide this?

#32

also is there a bug bounty for thisā€¦ this was never going to work with nginxā€¦ itā€™s been hours just to find out its something that was never going to work

#33

If itā€™s still trying to call localhost:1337, it means you havenā€™t deployed the changes properly to use futuro.money/server. It is still using the localhost server you set previously.

#34

maybe itā€™s nextjsā€¦

if thereā€™s nothing else besides

        <MoralisProvider appId="001" serverUrl="http://www.futuro.money/server" initializeOnMount={true}>
            <Layout>
              <Component {...pageProps} />
            </Layout>
        </MoralisProvider>

and the .env.local file

REACT_APP_SERVER_URL=http://futuro.money
REACT_APP_APPLICATION_ID=001

then what else am I missing?

#35

you see the error is coming from right?
ā€œnode_modules/moralis-v1/lib/browser/RESTController.js (445:0)ā€

This is how YOUR moralis-v1 worksā€¦

Screen Shot 2022-11-07 at 11.42.16 AM
Screen Shot 2022-11-07 at 11.42.16 AM3016Ɨ1756 264 KB

#36

you guys know .env is only accessible server side with nextjs right?

you are all all over the freaking place with your docsā€¦ your primary docs suggest nextjsā€¦ now you are using things that donā€™t work with the what you recommendā€¦ Iā€™ve wasted a whole freaking day on thisā€¦

#37

What is the actual code youā€™re using? In this code you have hardcoded the appId and serverUrl but youā€™re posting about using environment variables - thereā€™s no use of process.env here. Just hardcode them for now, donā€™t worry about the use of .env.local.

This is how YOUR moralis-v1 worksā€¦

Yes but your NFTea.app is still trying to connect to localhost:1337. This is from your own configuration (in MoralisProvider). Check the Moralis code for your deployed site for which serverUrl is actually being used. Make sure youā€™re not using another MoralisProvider or Moralis.start code anywhere.

#38

my friendā€¦
Iā€™ve told you the same thing a few different timesā€¦

regardless what is
hereā€¦ <MoralisProvider appId="001" serverUrl="http://www.futuro.money/server" initializeOnMount={true}>

Your node_modules/moralis-v1/lib/browser/RESTController.js (445:0)
script is ignoring thatā€¦

itā€™s looking for what is in the .env fileā€¦

var url = _CoreManager.default.get('SERVER_URL');

itā€™s not reading the .env fileā€¦ so it defaults to localhost:1337

thatā€™s not going to work with nginxā€¦

this is either because of nextjs not giving it access to the .env fileā€¦
or whatever reasonā€¦ itā€™s not me telling it to use localhostā€¦

if we are on the same page nowā€¦ can I please get a solution?

#39

Hey did u try using NEXT_PUBLIC_ instead of REACT_APP_ as the prefix of your nextjs app, otherwise it wonā€™t load your env variables

#40

yes I didā€¦ doesnā€™t work