Routing 404 error when published Angular 7 app

Asked Dec 31 '18 at 10:45

Active Dec 31 '18 at 10:45

Viewed 556 times

I have an angular 7 application. My application working my local without any problem. But when I published, I get 404 error. I'm using PathLocationService. Providers part of app.module.ts is like below. I tried also publishing by ng build --prod --aot --source-map=false --base-href. But, also not worked. What can be the reason of this? (When I go www.mywebsite.com/index.html I can see my loading bar. But www.mywebsite.com/MyPage then I get 404 error.)

  providers: [
    { provide: HTTP_INTERCEPTORS, useClass: LoaderInterceptor, multi: true },
    UserService, DatePipe, AuthGuard, RoleGuard, FormBuilder
  ],

asked Dec 31 '18 at 10:45

realist

2,155
12
38
77

2

Which webserver are you using to serve your application? apache for example needs a htaccess file to support the routing. – maio290 Dec 31 '18 at 10:47
I'm using IIS (Windows server 2012 R2). @maio290 – realist Dec 31 '18 at 10:49
1

See https://stackoverflow.com/a/44600609/4934937 – maio290 Dec 31 '18 at 10:49
I used --base-href as follows - `ng build --prod --aot --source-map=false --base-href ./` & got it working on IIS – Tushar Walzade Dec 31 '18 at 10:53
2

Your must always fallback to index.html to work. See this [official link](https://angular.io/guide/deployment#routed-apps-must-fallback-to-indexhtml) – KiraAG Dec 31 '18 at 10:53
I tried add web.config from your link. My 404 error gone. But now, I'm taking `Unexpected token <` error @maio290 – realist Dec 31 '18 at 11:00
1

Unexpected token is a javascript error, this does have nothing in common with the routing. – maio290 Dec 31 '18 at 11:01
But, I think it dependent to publishing. Because, in my local I didn't take any error or warning. @maio290 – realist Dec 31 '18 at 11:06
1

Yeah, but that's not related to the question here and you should try to find the error on your own. You got the console, you got the source code :) – maio290 Dec 31 '18 at 11:07
Ok. Thanks a lot @maio290 . If you write as an answer your first comment. Then I can mark as an answer. – realist Dec 31 '18 at 11:09
That not worked @TusharWalzade – realist Dec 31 '18 at 11:09
try that without using .htaccess or web.config – Tushar Walzade Dec 31 '18 at 11:10
1

Actually, @KiraAG had the better answer imho - the reason why is better explained on the Angular page itself, so I guess he'd deserve the Karma more ;) – maio290 Dec 31 '18 at 11:10
You're very fair man :) Thanks @maio290 – realist Dec 31 '18 at 11:14
I removed web.config but also not worked @TusharWalzade – realist Dec 31 '18 at 11:15

Routing 404 error when published Angular 7 app

0 Answers0